CVE-2022-4967 json
strongSwan versions 5.9.2 through 5.9.5 are affected by authorization bypass through improper validation of certificate with host mismatch…
published 2024-05-13 2 y ago modified 2026-06-17 4 mo ago also EUVD-2022-52219
- cvss
- 7.7
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
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).
Patch / fix
- strongSwan strongSwan 5.9.6
- strongswan Debian 14, Debian 13, Debian 12 5.9.6-1
debian advisories DEBIAN-CVE-2022-4967
- strongswan Ubuntu 22.04 LTS 5.9.5-2ubuntu2.3
ubuntu advisories UBUNTU-CVE-2022-4967
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-4967 updated cvss 7.7
strongswan: potential authorization bypass with TLS-based EAP methods
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.46% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.7 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N |
Affected products
- strongSwan strongSwan
References
-
github.com
/strongswan/strongswan/commit/e4b4aabc4996fc61c37deab7858d07bc4d220136
patch
-
strongswan.org
/blog/2024/05/13/strongswan-vulnerability-(cve-2022-4967).html
vendor-advisory, mitigation
-
cve.org
/CVERecord?id=CVE-2022-4967
issue-tracking, third-party-advisory
-
security.netapp.com
/advisory/ntap-20240614-0006/
third-party-advisory
Sources
- CVE List CVE-2022-4967
- NVD CVE-2022-4967
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.