{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2020-35684 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35684 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35684 is a high-severity memory corruption vulnerability in n/a, published on 19 Aug 2021. 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-35684 and fix it if it is affected.\n\nWhat it is: CVE-2020-35684 is a high-severity memory corruption vulnerability in n/a, published on 19 Aug 2021. 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-35684 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-35684/ (Markdown: https://insights.sbomify.com/CVE-2020-35684/index.md)","id":"CVE-2020-35684","markdown":"https://insights.sbomify.com/CVE-2020-35684/index.md","name":"CVE-2020-35684","record":{"aliases":["GHSA-748v-rhfv-4hm6"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"HCC Nichestack","requires_auth":"none","summary":"Attackers can trigger out-of-bounds reads or writes in TCP packet parsing by manipulating IP payload size fields, potentially causing crashes or information disclosure.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nichestack","vendor":"hcc-embedded"},{"product":"sentron_3wa_com190_firmware","vendor":"siemens"},{"product":"sentron_3wl_com35_firmware","vendor":"siemens"}],"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-20","name":"Improper Input Validation"}],"description":"An issue was discovered in HCC Nichestack 3.0. The code that parses TCP packets relies on an unchecked value of the IP payload size (extracted from the IP header) to compute the length of the TCP payload within the TCP checksum computation function. When the IP payload size is set to be smaller than the size of the IP header, the TCP checksum computation function may read out of bounds (a low-impact write-out-of-bounds is also possible).","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":"Memory corruption in n/a","id":"CVE-2020-35684","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2020-35685"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-35683"},"products":["n/a"],"published":"2021-08-19","related":[{"cvss_score":9.1,"headline":"Weak cryptography in n/a","id":"CVE-2020-35685","kev_date_added":null,"published":"2021-08-19"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2020-35683","kev_date_added":null,"published":"2021-08-19"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2021-27565","kev_date_added":null,"published":"2021-08-19"},{"cvss_score":7.5,"headline":"Memory corruption in n/a","id":"CVE-2021-31227","kev_date_added":null,"published":"2021-08-19"},{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2021-31228","kev_date_added":null,"published":"2021-08-19"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2021-31400","kev_date_added":null,"published":"2021-08-19"}],"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 or writes in TCP packet parsing by manipulating IP payload size fields, potentially causing crashes or information disclosure.","url":"https://insights.sbomify.com/CVE-2020-35684/"}