{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-17441 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-17441 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-17441 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-17441 and fix it if it is affected.\n\nWhat it is: CVE-2020-17441 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-17441 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-17441/ (Markdown: https://insights.sbomify.com/CVE-2020-17441/index.md)","id":"CVE-2020-17441","markdown":"https://insights.sbomify.com/CVE-2020-17441/index.md","name":"CVE-2020-17441","record":{"aliases":["GHSA-q3g8-363q-g9qq"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"picoTCP network stack","requires_auth":"none","summary":"Attackers can trigger out-of-bounds reads in picoTCP via malformed IPv6 headers, leading to information disclosure or denial of service.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"picotcp","vendor":"altran"},{"product":"mplab_harmony","vendor":"microchip"}],"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 picoTCP 1.7.0. The code for processing the IPv6 headers does not validate whether the IPv6 payload length field is equal to the actual size of the payload, which leads to an Out-of-Bounds read during the ICMPv6 checksum calculation, resulting in either Denial-of-Service or Information Disclosure. This affects pico_ipv6_extension_headers and pico_checksum_adder (in pico_ipv6.c and pico_frame.c).","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-17441","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":"Integer overflow in n/a","id":"CVE-2020-17442"},"packages":[],"prev":{"headline":"Null dereference in n/a","id":"CVE-2020-17440"},"products":["n/a"],"published":"2020-12-11","related":[{"cvss_score":9.8,"headline":"Use after free in n/a","id":"CVE-2021-33304","kev_date_added":null,"published":"2023-02-15"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-24338","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-1000210","kev_date_added":null,"published":"2017-11-17"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2020-24341","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2023-30463","kev_date_added":null,"published":"2023-04-19"},{"cvss_score":7.5,"headline":"Integer overflow in n/a","id":"CVE-2020-17442","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 trigger out-of-bounds reads in picoTCP via malformed IPv6 headers, leading to information disclosure or denial of service.","url":"https://insights.sbomify.com/CVE-2020-17441/"}