{"answers":{"affected":"3 open source packages ship an affected version, including trust-dns-proto. It affects 1 product.","exploited":"There is no known exploitation of CVE-2018-20994 in the wild and no public exploit code.","fix":"Upgrade trust-dns-proto to 0.4.3 or later.","what":"CVE-2018-20994 is a high-severity denial of service vulnerability in n/a, published on 26 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-20994 and fix it if it is affected.\n\nWhat it is: CVE-2018-20994 is a high-severity denial of service vulnerability in n/a, published on 26 Aug 2019. 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-2018-20994 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- trust-dns-proto (crates.io): affected all versions; fixed in 0.4.3\n- trust-dns-proto (crates.io): affected all versions; fixed in 0.4.3\n- trust-dns-proto (crates.io): affected from 0.0.0-0; fixed in 0.4.3\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-2018-20994/ (Markdown: https://insights.sbomify.com/CVE-2018-20994/index.md)","id":"CVE-2018-20994","markdown":"https://insights.sbomify.com/CVE-2018-20994/index.md","name":"CVE-2018-20994","record":{"aliases":["GHSA-369h-pjr2-6wrh","RUSTSEC-2018-0007"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust DNS library","requires_auth":"none","summary":"Attackers can cause a denial of service via infinite recursion in the trust-dns-proto crate due to mishandled DNS message compression.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"trust-dns-proto","vendor":"trust-dns-proto_project"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.0"},"cwes":[{"id":"CWE-674","name":"Uncontrolled Recursion"}],"description":"An issue was discovered in the trust-dns-proto crate before 0.5.0-alpha.3 for Rust. There is infinite recursion because DNS message compression is mishandled.","ecosystems":["crates.io"],"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":"Uncontrolled recursion in trust-dns-proto","id":"CVE-2018-20994","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"denial_of_service","year":"2018"},"n_packages":3,"n_references":1,"next":{"headline":"Memory corruption slice-deque","id":"CVE-2018-20995"},"packages":[{"ecosystem":"crates.io","fixed":["0.4.3"],"introduced":["0"],"last_affected":[],"package":"trust-dns-proto","purl":null,"source":"GHSA-369h-pjr2-6wrh"},{"ecosystem":"crates.io","fixed":["0.4.3"],"introduced":["0"],"last_affected":[],"package":"trust-dns-proto","purl":"pkg:cargo/trust-dns-proto","source":"GHSA-369h-pjr2-6wrh"},{"ecosystem":"crates.io","fixed":["0.4.3"],"introduced":["0.0.0-0"],"last_affected":[],"package":"trust-dns-proto","purl":"pkg:cargo/trust-dns-proto","source":"RUSTSEC-2018-0007"}],"prev":{"headline":"Uncontrolled recursion in rust-yaml","id":"CVE-2018-20993"},"products":["n/a"],"published":"2019-08-26","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":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"},{"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-05","vendors":["n/a"]},"summary":"Attackers can cause a denial of service via infinite recursion in the trust-dns-proto crate due to mishandled DNS message compression.","url":"https://insights.sbomify.com/CVE-2018-20994/"}