{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-19861 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-19861 is a high-severity vulnerability in n/a, published on 21 Jan 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-2020-19861 and fix it if it is affected.\n\nWhat it is: CVE-2020-19861 is a high-severity vulnerability in n/a, published on 21 Jan 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-2020-19861 in the wild and no public exploit code.\n\nAffected product: n/a. 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-2020-19861/ (Markdown: https://insights.sbomify.com/CVE-2020-19861/index.md)","id":"CVE-2020-19861","markdown":"https://insights.sbomify.com/CVE-2020-19861/index.md","name":"CVE-2020-19861","record":{"aliases":["DEBIAN-CVE-2020-19861","GHSA-fhv5-v23r-vj74","UBUNTU-CVE-2020-19861"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ldns DNS library","requires_auth":"none","summary":"A heap overflow in ldns allows attackers to leak sensitive memory information by parsing a maliciously crafted zone file.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"ldns","vendor":"nlnetlabs"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"When a zone file in ldns 1.7.1 is parsed, the function ldns_nsec3_salt_data is too trusted for the length value obtained from the zone file. When the memcpy is copied, the 0xfe - ldns_rdf_size(salt_rdf) byte data can be copied, causing heap overflow information leakage.","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":"Information disclosure in n/a","id":"CVE-2020-19861","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in n/a","id":"CVE-2020-19877"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2020-19860"},"products":["n/a"],"published":"2022-01-21","related":[{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2017-1000231","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2017-1000232","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":8.2,"headline":"Insufficient verification that responses belong to a query","id":"CVE-2026-10846","kev_date_added":null,"published":"2026-06-10"},{"cvss_score":6.8,"headline":"Memory corruption in n/a","id":"CVE-2011-3581","kev_date_added":null,"published":"2011-11-04"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2020-19860","kev_date_added":null,"published":"2022-01-21"},{"cvss_score":6.4,"headline":"Memory corruption in n/a","id":"CVE-2009-1086","kev_date_added":null,"published":"2009-03-25"}],"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":"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-04","vendors":["n/a"]},"summary":"A heap overflow in ldns allows attackers to leak sensitive memory information by parsing a maliciously crafted zone file.","url":"https://insights.sbomify.com/CVE-2020-19861/"}