{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-17439 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-17439 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-17439 is a high-severity 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-17439 and fix it if it is affected.\n\nWhat it is: CVE-2020-17439 is a high-severity 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-17439 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-17439/ (Markdown: https://insights.sbomify.com/CVE-2020-17439/index.md)","id":"CVE-2020-17439","markdown":"https://insights.sbomify.com/CVE-2020-17439/index.md","name":"CVE-2020-17439","record":{"aliases":["GHSA-5xvj-fmm7-pv9c"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"uIP network stack","requires_auth":"none","summary":"Attackers can poison the DNS cache in uIP by sending spoofed replies, leading to traffic redirection or data modification.","user_interaction":"not_required","vuln_class":"other"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"uip","vendor":"uip_project"}],"cvss":{"score":8.3,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"description":"An issue was discovered in uIP 1.0, as used in Contiki 3.0 and other products. The code that parses incoming DNS packets does not validate that the incoming DNS replies match outgoing DNS queries in newdata() in resolv.c. Also, arbitrary DNS replies are parsed if there was any outgoing DNS query with a transaction ID that matches the transaction ID of an incoming reply. Provided that the default DNS cache is quite small (only four records) and that the transaction ID has a very limited set of values that is quite easy to guess, this can lead to DNS cache poisoning.","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":"Other in n/a","id":"CVE-2020-17439","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"other","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Null dereference in n/a","id":"CVE-2020-17440"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-17438"},"products":["n/a"],"published":"2020-12-11","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-17438","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":8.2,"headline":"Denial of service in n/a","id":"CVE-2020-24334","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2020-24335","kev_date_added":null,"published":"2021-02-02"},{"cvss_score":7.5,"headline":"Null dereference in n/a","id":"CVE-2020-17440","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":"Attackers can poison the DNS cache in uIP by sending spoofed replies, leading to traffic redirection or data modification.","url":"https://insights.sbomify.com/CVE-2020-17439/"}