CVE-2022-4967 [High] | Security Bypass in Strongswan

strongSwan versions 5.9.2 through 5.9.5 are affected by authorization bypass through improper validation of certificate with host mismatch (CWE-297). When certificates are used to authenticate clients in TLS-based EAP methods, the IKE or EAP identity supplied by a client is not enforced to be contained in the client's certificate. So clients can authenticate with any trusted certificate and claim an arbitrary IKE/EAP identity as their own. This is problematic if the identity is used to make policy decisions. A fix was released in strongSwan version 5.9.6 in August 2022 (e4b4aabc4996fc61c37deab7858d07bc4d220136).

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.05%	0.46%	+0.42%
2	2025-11-21	0.14%	0.05%	-0.10%
3	2025-11-18	—	0.14%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.05%

0.46%

+0.42%

2025-11-21

0.14%

0.05%

-0.10%

2025-11-18

—

0.14%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
7.7	3.1	HIGH	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	3.1	4.0	[email protected]
6.5	3.1	MEDIUM	`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N` Click to expand Attack vector (AV:N) Could be attacked over the internet or any normal routed network—not just someone sitting at the machine. Attack complexity (AC:L) Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup. Privileges required (PR:L) A normal user session is enough; they don’t have to be admin. User interaction (UI:N) Nobody has to click “OK” or open a trap file; it can work without a victim helping. Scope (S:U) Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	2.8	3.6	[email protected]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

7.7

3.1

HIGH

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

3.1

4.0

[email protected]

6.5

3.1

MEDIUM

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand

Attack vector (AV:N): Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L): Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L): A normal user session is enough; they don’t have to be admin.
User interaction (UI:N): Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U): Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

2.8

3.6

[email protected]

OS Trackers for CVE-2022-4967

vendor	priority	summary	link
`debian`	unimportant	CVE-2022-4967 unimportant priority: Debian including 1 source packages (strongswan), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5.	https://security-tracker.debian.org/tracker/CVE-2022-4967
`ubuntu`	medium	CVE-2022-4967 medium priority: Ubuntu including 1 source packages (strongswan), 8 status rows across 8 suites (bionic, focal, jammy, mantic, noble, trusty, upstream, xenial): not-affected 6, released 2.	https://ubuntu.com/security/CVE-2022-4967

Affected software / configurations for CVE-2022-4967

Vendor	Product	Version	Raw CPE
strongswan	strongswan	>= 5.9.2, < 5.9.6	cpe:2.3:a:strongswan:strongswan::::::::

References for CVE-2022-4967

URL	Tags
https://github.com/strongswan/strongswan/commit/e4b4aabc4996fc61c37deab7858d07bc4d220136	Patch
https://security.netapp.com/advisory/ntap-20240614-0006/	Third Party Advisory
https://www.cve.org/CVERecord?id=CVE-2022-4967	Third Party Advisory
https://www.strongswan.org/blog/2024/05/13/strongswan-vulnerability-(cve-2022-4967).html	Mitigation Vendor Advisory

URL

CVE-2022-4967

Exploit prediction scoring system (EPSS) score for CVE-2022-4967

Common vulnerability scoring system (CVSS) metrics for CVE-2022-4967

Weakness enumeration for CVE-2022-4967

OS Trackers for CVE-2022-4967

Affected software / configurations for CVE-2022-4967

References for CVE-2022-4967