{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2020-24337 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-24337 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-24337 is a high-severity denial of service 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-24337 and fix it if it is affected.\n\nWhat it is: CVE-2020-24337 is a high-severity denial of service 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-24337 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-24337/ (Markdown: https://insights.sbomify.com/CVE-2020-24337/index.md)","id":"CVE-2020-24337","markdown":"https://insights.sbomify.com/CVE-2020-24337/index.md","name":"CVE-2020-24337","record":{"aliases":["GHSA-m89x-hf4g-3j36"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"picoTCP network stack","requires_auth":"none","summary":"An attacker can cause a denial of service in picoTCP by sending a TCP packet with an unsupported zero-length option, triggering an infinite loop.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"picotcp","vendor":"altran"},{"product":"picotcp-ng","vendor":"altran"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-835","name":"Loop with Unreachable Exit Condition"}],"description":"An issue was discovered in picoTCP and picoTCP-NG through 1.7.0. When an unsupported TCP option with zero length is provided in an incoming TCP packet, it is possible to cause a Denial-of-Service by achieving an infinite loop in the code that parses TCP options, aka tcp_parse_options() in pico_tcp.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":"Denial of service in n/a","id":"CVE-2020-24337","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2020-24338"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-24336"},"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":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":"An attacker can cause a denial of service in picoTCP by sending a TCP packet with an unsupported zero-length option, triggering an infinite loop.","url":"https://insights.sbomify.com/CVE-2020-24337/"}