{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-66647 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-66647 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66647 is a low-severity memory corruption vulnerability in RIOT-OS RIOT, published on 17 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-66647 and fix it if it is affected.\n\nWhat it is: CVE-2025-66647 is a low-severity memory corruption vulnerability in RIOT-OS RIOT, published on 17 Dec 2025. 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-2025-66647 in the wild and no public exploit code.\n\nAffected product: RIOT-OS RIOT. 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-2025-66647/ (Markdown: https://insights.sbomify.com/CVE-2025-66647/index.md)","id":"CVE-2025-66647","markdown":"https://insights.sbomify.com/CVE-2025-66647/index.md","name":"CVE-2025-66647","record":{"aliases":["GHSA-wh3v-q6vr-j79r"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":true,"product_category":"RIOT OS","requires_auth":"none","summary":"Attacker can trigger buffer overflow in IPv6 reassembly to corrupt memory and potentially execute code on IoT devices using RIOT OS.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"riot","vendor":"riot-os"}],"cvss":{"score":1.7,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:U","version":"4.0"},"cwes":[{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"RIOT is an open-source microcontroller operating system, designed to match the requirements of Internet of Things (IoT) devices and other embedded devices. A vulnerability was discovered in the IPv6 fragmentation reassembly implementation of RIOT OS v2025.07. When copying the contents of the first fragment (offset=0) into the reassembly buffer, no size check is performed. It is possible to force the creation of a small reassembly buffer by first sending a shorter fragment (also with offset=0). Overflowing the reassembly buffer corrupts the state of other packet buffers which an attacker might be able to used to achieve further memory corruption (potentially resulting in remote code execution). To trigger the vulnerability, the `gnrc_ipv6_ext_frag` module must be included and the attacker must be able to send arbitrary IPv6 packets to the victim. Version 2025.10 fixes the issue.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"RIOT OS has buffer overflow in gnrc_ipv6_ext_frag_reass","id":"CVE-2025-66647","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":6,"next":{"headline":"`vega-functions` vulnerable to Cross-site Scripting via `setdata` function","id":"CVE-2025-66648"},"packages":[],"prev":{"headline":"RIOT-OS has NULL pointer dereference in gnrc_ipv6_ext_frag_reass","id":"CVE-2025-66646"},"products":["RIOT"],"published":"2025-12-17","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-17","vendors":["RIOT-OS"]},"summary":"Attacker can trigger buffer overflow in IPv6 reassembly to corrupt memory and potentially execute code on IoT devices using RIOT OS.","url":"https://insights.sbomify.com/CVE-2025-66647/"}