{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-24341 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-24341 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-24341 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-24341 and fix it if it is affected.\n\nWhat it is: CVE-2020-24341 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-24341 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-24341/ (Markdown: https://insights.sbomify.com/CVE-2020-24341/index.md)","id":"CVE-2020-24341","markdown":"https://insights.sbomify.com/CVE-2020-24341/index.md","name":"CVE-2020-24341","record":{"aliases":["GHSA-qj3c-vm3g-g389"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"picoTCP networking library","requires_auth":"none","summary":"Attackers can trigger an out-of-bounds read in picoTCP, 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":"picotcp-ng","vendor":"altran"}],"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 and picoTCP-NG through 1.7.0. The TCP input data processing function in pico_tcp.c does not validate the length of incoming TCP packets, which leads to an out-of-bounds read when assembling received packets into a data segment, eventually causing Denial-of-Service or an information leak.","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-24341","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":"Memory corruption in n/a","id":"CVE-2020-24342"},"packages":[],"prev":{"headline":"Denial of service in n/a","id":"CVE-2020-24340"},"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-17441","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 an out-of-bounds read in picoTCP, leading to information disclosure or denial of service.","url":"https://insights.sbomify.com/CVE-2020-24341/"}