Authorization bypass via certificate subject lookup
Published May 13, 2024 · Updated Feb 13, 2025
Authorization bypass in strongSwan 5.9.2 through 5.9.5 allows remote authenticated users to assume arbitrary IKE or EAP identities. On the TLS server, libtls looks up a trusted client public key by the presented certificate's subject DN instead of the client-supplied identity. Exploitation requires a trusted client certificate, a TLS-based EAP method, and policy decisions tied to the claimed identity; it grants only the access assigned to that identity.
Summary
What happened
Authorization bypass in strongSwan 5.9.2 through 5.9.5 allows remote authenticated users to assume arbitrary IKE or EAP identities. On the TLS server, libtls looks up a trusted client public key by the presented certificate's subject DN instead of the client-supplied identity. Exploitation requires a trusted client certificate, a TLS-based EAP method, and policy decisions tied to the claimed identity; it grants only the access assigned to that identity.
The record
- CVE
- CVE-2022-4967
- Published
- May 13, 2024
- Updated
- Feb 13, 2025
- Vendor
- strongSwan
- Product
- strongSwan
- Classifications
- CWE-297, T1133
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 13, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.9.2 <5.9.6
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo