{"answers":{"affected":"2 open source packages ship an affected version, including github.com/coredns/coredns. It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-2837 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-2837 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-2837 is a medium-severity vulnerability in coreDNS, published on 3 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-2837 and fix it if it is affected.\n\nWhat it is: CVE-2022-2837 is a medium-severity vulnerability in coreDNS, published on 3 Mar 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-2837 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/coredns/coredns (Go): affected all versions up to 1.9.3; no fix listed\n- github.com/coredns/coredns (Go): affected all versions up to 1.9.3; 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-2837/ (Markdown: https://insights.sbomify.com/CVE-2022-2837/index.md)","id":"CVE-2022-2837","markdown":"https://insights.sbomify.com/CVE-2022-2837/index.md","name":"CVE-2022-2837","record":{"aliases":["GHSA-h828-v5pv-33qx"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"CoreDNS server","requires_auth":"none","summary":"Attackers can redirect external TLD traffic to malicious pods by creating matching namespaces, potentially intercepting data or bypassing security controls.","user_interaction":"required","vuln_class":"open_redirect"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"redhat","cpe":[{"product":"coredns","vendor":"coredns.io"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-601","name":"URL Redirection to Untrusted Site"},{"id":"CWE-923","name":"Improper Restriction of Communication Channel to Intended Endpoints"}],"description":"A flaw was found in coreDNS. This flaw allows a malicious user to redirect traffic intended for external top-level domains (TLD) to a pod they control by creating projects and namespaces that match the TLD.","ecosystems":["Go"],"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":"coreDNS vulnerable to Improper Restriction of Communication Channel to Intended Endpoints","id":"CVE-2022-2837","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"open_redirect","year":"2022"},"n_packages":2,"n_references":1,"next":{"headline":"XML external entity in Eclipse Sphinx","id":"CVE-2022-2838"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":["1.9.3"],"package":"github.com/coredns/coredns","purl":null,"source":"GHSA-h828-v5pv-33qx"},{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":["1.9.3"],"package":"github.com/coredns/coredns","purl":"pkg:golang/github.com/coredns/coredns","source":"GHSA-h828-v5pv-33qx"}],"prev":{"headline":"coreDNS vulnerable to Improper Restriction of Communication Channel to Intended Endpoints","id":"CVE-2022-2835"},"products":["coreDNS"],"published":"2023-03-03","related":[{"cvss_score":8.7,"headline":"CoreDNS DNS-over-QUIC unbounded goroutine growth leads to denial of service","id":"CVE-2026-32934","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.7,"headline":"CoreDNS DoH GET path missing size validation causes CPU and memory amplification","id":"CVE-2026-32936","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.7,"headline":"CoreDNS TSIG authentication bypass on encrypted DNS transports","id":"CVE-2026-33190","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.2,"headline":"CoreDNS transfer plugin subzone ACL bypass via lexicographic zone comparison","id":"CVE-2026-33489","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":8.2,"headline":"CoreDNS TSIG authentication bypass on gRPC, QUIC, DoH, and DoH3 transports","id":"CVE-2026-35579","kev_date_added":null,"published":"2026-05-05"},{"cvss_score":7.7,"headline":"CoreDNS ACL Bypass","id":"CVE-2026-26017","kev_date_added":null,"published":"2026-03-06"},{"cvss_score":7.5,"headline":"CoreDNS: proxyproto plugin panics on PPv2 datagram with non-UDP transport — single 28-byte packet remote DoS","id":"CVE-2026-62309","kev_date_added":null,"published":"2026-07-16"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-07","vendors":["n/a"]},"summary":"Attackers can redirect external TLD traffic to malicious pods by creating matching namespaces, potentially intercepting data or bypassing security controls.","url":"https://insights.sbomify.com/CVE-2022-2837/"}