{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-31663 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-31663 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-31663 is a high-severity memory corruption vulnerability in n/a, published on 18 Jun 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-2021-31663 and fix it if it is affected.\n\nWhat it is: CVE-2021-31663 is a high-severity memory corruption vulnerability in n/a, published on 18 Jun 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-2021-31663 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-2021-31663/ (Markdown: https://insights.sbomify.com/CVE-2021-31663/index.md)","id":"CVE-2021-31663","markdown":"https://insights.sbomify.com/CVE-2021-31663/index.md","name":"CVE-2021-31663","record":{"aliases":["GHSA-hgwj-h89r-w966"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"RIOT-OS","requires_auth":"none","summary":"A buffer overflow in RIOT-OS allows attackers to obtain sensitive information, requiring a patch to mitigate the risk.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"riot","vendor":"riot-os"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"RIOT-OS 2021.01 before commit bc59d60be60dfc0a05def57d74985371e4f22d79 contains a buffer overflow which could allow attackers to obtain sensitive information.","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-2021-31663","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2021"},"n_packages":0,"n_references":3,"next":{"headline":"Memory corruption in n/a","id":"CVE-2021-31664"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2021-31662"},"products":["n/a"],"published":"2021-06-18","related":[{"cvss_score":9.8,"headline":"Buffer overflows in RIOT","id":"CVE-2024-32017","kev_date_added":null,"published":"2024-05-01"},{"cvss_score":9.8,"headline":"RIOT-OS vulnerable to Out of Bounds Write in _rbuf_add","id":"CVE-2023-33975","kev_date_added":null,"published":"2023-05-30"},{"cvss_score":9.8,"headline":"RIOT-OS vulnerable to Buffer Overflow during IPHC receive","id":"CVE-2023-24819","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":9.8,"headline":"RIOT-OS vulnerable to Packet Type Confusion during IPHC send","id":"CVE-2023-24823","kev_date_added":null,"published":"2023-04-24"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-27357","kev_date_added":null,"published":"2021-04-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-27697","kev_date_added":null,"published":"2021-04-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2021-27698","kev_date_added":null,"published":"2021-04-06"}],"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-03","vendors":["n/a"]},"summary":"A buffer overflow in RIOT-OS allows attackers to obtain sensitive information, requiring a patch to mitigate the risk.","url":"https://insights.sbomify.com/CVE-2021-31663/"}