{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-17467 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-17467 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-17467 is a critical vulnerability in n/a, published on 11 Dec 2020. 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-17467 and fix it if it is affected.\n\nWhat it is: CVE-2020-17467 is a critical vulnerability in n/a, published on 11 Dec 2020. 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-17467 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-17467/ (Markdown: https://insights.sbomify.com/CVE-2020-17467/index.md)","id":"CVE-2020-17467","markdown":"https://insights.sbomify.com/CVE-2020-17467/index.md","name":"CVE-2020-17467","record":{"aliases":["GHSA-wvw6-x7x2-94g8"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"FNET TCP/IP stack","requires_auth":"none","summary":"A missing null termination check in FNET's LLMNR processing allows attackers to read sensitive memory contents via malicious requests.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"fnet","vendor":"butok"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"An issue was discovered in FNET through 4.6.4. The code for processing the hostname from an LLMNR request doesn't check for '\\0' termination. Therefore, the deduced length of the hostname doesn't reflect the correct length of the actual data. This may lead to Information Disclosure in _fnet_llmnr_poll in fnet_llmnr.c during a response to a malicious request of the DNS class IN.","ecosystems":[],"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":"Information disclosure in n/a","id":"CVE-2020-17467","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Denial of service in n/a","id":"CVE-2020-17468"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2020-17466"},"products":["n/a"],"published":"2020-12-11","related":[{"cvss_score":9.1,"headline":"Weak cryptography in n/a","id":"CVE-2020-27633","kev_date_added":null,"published":"2023-10-10"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2020-24383","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2020-17468","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2020-17469","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":5.3,"headline":"Weak cryptography in n/a","id":"CVE-2020-17470","kev_date_added":null,"published":"2020-12-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":"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 missing null termination check in FNET's LLMNR processing allows attackers to read sensitive memory contents via malicious requests.","url":"https://insights.sbomify.com/CVE-2020-17467/"}