{"answers":{"affected":"It affects 3 products.","exploited":"There is no known exploitation of CVE-2020-35685 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-35685 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-35685 is a critical 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-35685 and fix it if it is affected.\n\nWhat it is: CVE-2020-35685 is a critical 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-35685 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-35685/ (Markdown: https://insights.sbomify.com/CVE-2020-35685/index.md)","id":"CVE-2020-35685","markdown":"https://insights.sbomify.com/CVE-2020-35685/index.md","name":"CVE-2020-35685","record":{"aliases":["GHSA-hf8h-gvq7-6gfr"],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"HCC Nichestack TCP stack","requires_auth":"none","summary":"Attackers can predict TCP Initial Sequence Numbers to hijack existing connections or spoof future ones due to insufficient randomness in the HCC Nichestack implementation.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"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":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"An issue was discovered in HCC Nichestack 3.0. The code that generates Initial Sequence Numbers (ISNs) for TCP connections derives the ISN from an insufficiently random source. As a result, an attacker may be able to determine the ISN of current and future TCP connections and either hijack existing ones or spoof future ones. (Proper ISN generation should aim to follow at least the specifications outlined in RFC 6528.)","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":"Weak cryptography in n/a","id":"CVE-2020-35685","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Privilege escalation in n/a","id":"CVE-2020-35686"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2020-35684"},"products":["n/a"],"published":"2021-08-19","related":[{"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":"Memory corruption in n/a","id":"CVE-2020-35684","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 predict TCP Initial Sequence Numbers to hijack existing connections or spoof future ones due to insufficient randomness in the HCC Nichestack implementation.","url":"https://insights.sbomify.com/CVE-2020-35685/"}