{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-11904 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-11904 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-11904 is a high-severity vulnerability in n/a, published on 17 Jun 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-11904 and fix it if it is affected.\n\nWhat it is: CVE-2020-11904 is a high-severity vulnerability in n/a, published on 17 Jun 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-11904 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-11904/ (Markdown: https://insights.sbomify.com/CVE-2020-11904/index.md)","id":"CVE-2020-11904","markdown":"https://insights.sbomify.com/CVE-2020-11904/index.md","name":"CVE-2020-11904","record":{"aliases":["GHSA-3wmc-fg6p-fq4v"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Treck TCP/IP stack","requires_auth":"none","summary":"An integer overflow in the Treck TCP/IP stack allows out-of-bounds writes, potentially enabling remote code execution or denial of service.","user_interaction":"not_required","vuln_class":"integer_overflow"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"tcp\\/ip","vendor":"treck"}],"cvss":{"score":7.3,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-190","name":"Integer Overflow or Wraparound"}],"description":"The Treck TCP/IP stack before 6.0.1.66 has an Integer Overflow during Memory Allocation that causes an Out-of-Bounds Write.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Integer overflow in n/a","id":"CVE-2020-11904","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"integer_overflow","year":"2020"},"n_packages":0,"n_references":9,"next":{"headline":"Memory corruption in n/a","id":"CVE-2020-11905"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-11903"},"products":["n/a"],"published":"2020-06-17","related":[{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2020-25066","kev_date_added":null,"published":"2020-12-22"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2020-11896","kev_date_added":null,"published":"2020-06-17"},{"cvss_score":10,"headline":"Memory corruption in n/a","id":"CVE-2020-11897","kev_date_added":null,"published":"2020-06-17"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-11910","kev_date_added":null,"published":"2020-06-17"},{"cvss_score":9.1,"headline":"Information disclosure in n/a","id":"CVE-2020-11898","kev_date_added":null,"published":"2020-06-17"},{"cvss_score":9.1,"headline":"The Treck TCP/IP stack before 6.0.1.66 has an IPv4 Integer Underflow.","id":"CVE-2020-11909","kev_date_added":null,"published":"2020-06-17"},{"cvss_score":9,"headline":"Memory corruption in n/a","id":"CVE-2020-11901","kev_date_added":null,"published":"2020-06-17"}],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-09-30","vendors":["n/a"]},"summary":"An integer overflow in the Treck TCP/IP stack allows out-of-bounds writes, potentially enabling remote code execution or denial of service.","url":"https://insights.sbomify.com/CVE-2020-11904/"}