{"answers":{"affected":"2 open source packages ship an affected version, including org.zaproxy:zap. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-27820 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-27820 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-27820 is a medium-severity vulnerability in n/a, published on 24 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-27820 and fix it if it is affected.\n\nWhat it is: CVE-2022-27820 is a medium-severity vulnerability in n/a, published on 24 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-27820 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.zaproxy:zap (Maven): affected all versions up to 2.11.1; no fix listed\n- org.zaproxy:zap (Maven): affected all versions up to 2.11.1; no fix listed\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-27820/ (Markdown: https://insights.sbomify.com/CVE-2022-27820/index.md)","id":"CVE-2022-27820","markdown":"https://insights.sbomify.com/CVE-2022-27820/index.md","name":"CVE-2022-27820","record":{"aliases":["GHSA-j7xg-5549-jr3j"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"OWASP ZAP","requires_auth":"none","summary":"OWASP ZAP fails to verify TLS certificate chains, allowing attackers to bypass security checks and potentially intercept traffic.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"zed_attack_proxy","vendor":"owasp"}],"cvss":{"score":4,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"OWASP Zed Attack Proxy (ZAP) through w2022-03-21 does not verify the TLS certificate chain of an HTTPS server.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Improper Certificate Validation in OWASP ZAP","id":"CVE-2022-27820","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"security_feature_bypass","year":"2022"},"n_packages":2,"n_references":3,"next":{"headline":"Denial of service in Samsung Mobile Devices","id":"CVE-2022-27821"},"packages":[{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["2.11.1"],"package":"org.zaproxy:zap","purl":null,"source":"GHSA-j7xg-5549-jr3j"},{"ecosystem":"Maven","fixed":[],"introduced":["0"],"last_affected":["2.11.1"],"package":"org.zaproxy:zap","purl":"pkg:maven/org.zaproxy/zap","source":"GHSA-j7xg-5549-jr3j"}],"prev":{"headline":"Unsafe parsing in SWHKD","id":"CVE-2022-27819"},"products":["n/a"],"published":"2022-03-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-03","vendors":["n/a"]},"summary":"OWASP ZAP fails to verify TLS certificate chains, allowing attackers to bypass security checks and potentially intercept traffic.","url":"https://insights.sbomify.com/CVE-2022-27820/"}