{"id":"CVE-2022-4967","aliases":["DEBIAN-CVE-2022-4967","EUVD-2022-52219","GHSA-2hrc-c28p-9f59","UBUNTU-CVE-2022-4967","USN-6772-1"],"status":"published","title":"strongSwan versions 5.9.2 through 5.9.5 are affected by authorization bypass through improper...","description":"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).","severity":{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00464,"percentile":0.40493,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"published":"2024-05-13T12:09:19Z","modified":"2026-10-28T10:25:53Z","fixes":[{"ecosystem":"Debian:12","package":"strongswan","fixed_in":["5.9.6-1"],"sources":["osv"]},{"ecosystem":"Debian:13","package":"strongswan","fixed_in":["5.9.6-1"],"sources":["osv"]},{"ecosystem":"Debian:14","package":"strongswan","fixed_in":["5.9.6-1"],"sources":["osv"]},{"ecosystem":"Ubuntu:22.04:LTS","package":"strongswan","fixed_in":["5.9.5-2ubuntu2.3"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Debian:12","package":"strongswan","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.9.6-1"}]}]},{"source":"osv","ecosystem":"Debian:13","package":"strongswan","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.9.6-1"}]}]},{"source":"osv","ecosystem":"Debian:14","package":"strongswan","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.9.6-1"}]}]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"strongswan","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.9.5-2ubuntu2.3"}]}],"versions":["5.9.1-1ubuntu3","5.9.1-1ubuntu3.1","5.9.4-1ubuntu1","5.9.4-1ubuntu2","5.9.4-1ubuntu3","5.9.4-1ubuntu4","5.9.5-2ubuntu1","5.9.5-2ubuntu2","5.9.5-2ubuntu2.1","5.9.5-2ubuntu2.2"]},{"source":"osv","ecosystem":"Ubuntu:22.04:LTS","package":"strongswan","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.9.5-2ubuntu2.3"}]}],"versions":["5.9.1-1ubuntu3","5.9.1-1ubuntu3.1","5.9.4-1ubuntu1","5.9.4-1ubuntu2","5.9.4-1ubuntu3","5.9.4-1ubuntu4","5.9.5-2ubuntu1","5.9.5-2ubuntu2","5.9.5-2ubuntu2.1","5.9.5-2ubuntu2.2"]}],"products":[{"vendor":"strongswan","product":"strongswan"}],"references":[{"url":"https://github.com/strongswan/strongswan/commit/e4b4aabc4996fc61c37deab7858d07bc4d220136","tags":["patch","x_transferred","Patch","fix"]},{"url":"https://www.strongswan.org/blog/2024/05/13/strongswan-vulnerability-(cve-2022-4967).html","tags":["vendor-advisory","x_transferred","Mitigation","Vendor Advisory","advisory","report"]},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-4967","tags":["issue-tracking","x_transferred","Third Party Advisory","report"]},{"url":"https://security.netapp.com/advisory/ntap-20240614-0006/","tags":["x_transferred","Third Party Advisory","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-4967","tags":["advisory"]},{"url":"https://security.netapp.com/advisory/ntap-20240614-0006"},{"url":"https://github.com/advisories/GHSA-2hrc-c28p-9f59"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/4xxx/CVE-2022-4967.json","tags":["advisory"]},{"url":"https://github.com/strongswan/strongswan","tags":["package"]},{"url":"https://security-tracker.debian.org/tracker/CVE-2022-4967","tags":["advisory"]},{"url":"https://ubuntu.com/security/CVE-2022-4967","tags":["report"]},{"url":"https://ubuntu.com/security/notices/USN-6772-1","tags":["advisory"]}],"sources":{"cve":[{"id":"CVE-2022-4967","description":"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).","status":"published","published":"2024-05-13T12:09:19.104Z","modified":"2025-02-13T16:38:39.882Z","cvss":[{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","level":"high","assessor":"cna"}],"updated_at":"2026-11-02T14:34:37.932195Z"}],"euvd":[{"id":"EUVD-2022-52219","description":"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).","status":"published","published":"2024-05-13T12:09:19Z","modified":"2025-02-13T16:38:39Z","cvss":[{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","level":"high"}],"updated_at":"2026-11-03T00:03:52.297177Z"}],"ghsa":[{"id":"GHSA-2hrc-c28p-9f59","title":"strongSwan versions 5.9.2 through 5.9.5 are affected by authorization bypass through improper...","description":"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).","status":"published","published":"2024-05-14T18:30:45Z","modified":"2024-06-14T15:31:25Z","cvss":[{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","level":"high"}],"updated_at":"2026-11-02T14:57:29.798871Z"}],"nvd":[{"id":"CVE-2022-4967","description":"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).","status":"published","published":"2024-05-14T11:57:00.55Z","modified":"2026-06-17T05:22:26.443Z","cvss":[{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","level":"high","assessor":"secondary"},{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium","assessor":"primary"}],"updated_at":"2026-11-02T14:07:40.49892Z"}],"osv":[{"id":"CVE-2022-4967","description":"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).","status":"published","published":"2024-05-13T12:09:19.104Z","modified":"2026-10-28T10:25:53.926176401Z","cvss":[{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","level":"high"}],"updated_at":"2026-11-02T15:44:28.416025Z"},{"id":"UBUNTU-CVE-2022-4967","description":"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).","status":"published","published":"2024-05-13T18:00:00Z","modified":"2026-02-04T04:36:25.600335Z","cvss":[{"version":"3.1","score":7.7,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","level":"high"},{"version":"3.1","score":6.5,"vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","level":"medium"}],"updated_at":"2026-11-02T16:54:03.879901Z"},{"id":"DEBIAN-CVE-2022-4967","description":"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).","status":"published","published":"2024-05-14T11:57:00.55Z","modified":"2026-11-03T06:02:28.760282988Z","updated_at":"2026-11-03T06:44:05.456691Z"},{"id":"USN-6772-1","title":"strongswan vulnerability","description":"Jan Schermer discovered that strongSwan incorrectly validated client\ncertificates in certain configurations. A remote attacker could possibly\nuse this issue to bypass access controls.\n","status":"published","published":"2024-05-14T11:20:27Z","modified":"2026-02-10T04:43:48Z","updated_at":"2026-11-02T16:58:17.914523Z"}]}}