{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-27213 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-27213 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-27213 is a high-severity vulnerability in n/a, published on 10 Oct 2023. 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-27213 and fix it if it is affected.\n\nWhat it is: CVE-2020-27213 is a high-severity vulnerability in n/a, published on 10 Oct 2023. 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-27213 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-27213/ (Markdown: https://insights.sbomify.com/CVE-2020-27213/index.md)","id":"CVE-2020-27213","markdown":"https://insights.sbomify.com/CVE-2020-27213/index.md","name":"CVE-2020-27213","record":{"aliases":["GHSA-5wm2-v84q-jw9v"],"analysis":{"component_type":"operating_system","fix_type":"no_fix_stated","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Ethernut Nut/OS","requires_auth":"none","summary":"Insufficiently random TCP Initial Sequence Numbers in Ethernut Nut/OS allow attackers to hijack existing connections or spoof future ones.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"nut\\/os","vendor":"ethernut"}],"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:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"An issue was discovered in Ethernut Nut/OS 5.1. 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. While the ISN generator seems to adhere to RFC 793 (where a global 32-bit counter is incremented roughly every 4 microseconds), 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-27213","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":"Local Temp Directory Hijacking Vulnerability","id":"CVE-2020-27216"},"packages":[],"prev":{"headline":"Security feature bypass in n/a","id":"CVE-2020-27212"},"products":["n/a"],"published":"2023-10-10","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-25107","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-25108","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2020-25109","kev_date_added":null,"published":"2020-12-11"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2020-25110","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-09-19","vendors":["n/a"]},"summary":"Insufficiently random TCP Initial Sequence Numbers in Ethernut Nut/OS allow attackers to hijack existing connections or spoof future ones.","url":"https://insights.sbomify.com/CVE-2020-27213/"}