{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-4967 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2022-4967 is a high-severity authentication bypass vulnerability in strongSwan, published on 13 May 2024. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-4967 and fix it if it is affected.\n\nWhat it is: CVE-2022-4967 is a high-severity authentication bypass vulnerability in strongSwan, published on 13 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-4967 in the wild and no public exploit code.\n\nAffected product: strongSwan. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2022-4967/ (Markdown: https://insights.sbomify.com/CVE-2022-4967/index.md)","id":"CVE-2022-4967","markdown":"https://insights.sbomify.com/CVE-2022-4967/index.md","name":"CVE-2022-4967","record":{"aliases":["DEBIAN-CVE-2022-4967","GHSA-2hrc-c28p-9f59","UBUNTU-CVE-2022-4967","USN-6772-1"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"IPsec VPN software","requires_auth":"low_privilege","summary":"Attackers can bypass authentication in strongSwan by using any trusted certificate to claim arbitrary identities, potentially gaining unauthorized access.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"canonical","cpe":[{"product":"strongswan","vendor":"strongswan"}],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N","version":"3.1"},"cwes":[],"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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Auth bypass in strongSwan","id":"CVE-2022-4967","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Information disclosure in Netplan","id":"CVE-2022-4968"},"packages":[],"prev":{"headline":"sequentech admin-console Election Description cross site scripting","id":"CVE-2022-4966"},"products":["strongSwan"],"published":"2024-05-13","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-41913","kev_date_added":null,"published":"2023-12-07"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2023-26463","kev_date_added":null,"published":"2023-04-14"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2015-3991","kev_date_added":null,"published":"2017-09-07"},{"cvss_score":7.5,"headline":"Null dereference in strongSwan","id":"CVE-2026-78130","kev_date_added":null,"published":"2026-09-11"},{"cvss_score":7.5,"headline":"Denial of service in strongSwan","id":"CVE-2026-78132","kev_date_added":null,"published":"2026-09-11"},{"cvss_score":7.5,"headline":"Use after free in strongSwan","id":"CVE-2026-78133","kev_date_added":null,"published":"2026-09-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-13","vendors":["strongSwan"]},"summary":"Attackers can bypass authentication in strongSwan by using any trusted certificate to claim arbitrary identities, potentially gaining unauthorized access.","url":"https://insights.sbomify.com/CVE-2022-4967/"}