Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-66647: CWE-120: Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') in RIOT-OS RIOT

0
Low
VulnerabilityCVE-2025-66647cvecve-2025-66647cwe-120
Published: Wed Dec 17 2025 (12/17/2025, 20:21:13 UTC)
Source: CVE Database V5
Vendor/Project: RIOT-OS
Product: RIOT

Description

CVE-2025-66647 is a buffer overflow vulnerability in the IPv6 fragmentation reassembly implementation of RIOT-OS versions prior to 2025. 10. The flaw occurs because the system does not check the size when copying the first IPv6 fragment into the reassembly buffer, allowing an attacker to overflow this buffer by manipulating fragment sizes. This overflow can corrupt adjacent packet buffers, potentially enabling further memory corruption and remote code execution. Exploitation requires the vulnerable gnrc_ipv6_ext_frag module to be enabled and the ability to send arbitrary IPv6 packets to the target device. Although the CVSS score is low (1. 7), the vulnerability could be critical in specific IoT contexts where RIOT-OS is deployed. The issue is fixed in version 2025. 10, and no known exploits are currently reported in the wild.

AI-Powered Analysis

AILast updated: 12/24/2025, 20:46:40 UTC

Technical Analysis

RIOT-OS is an open-source operating system tailored for IoT and embedded devices, supporting IPv6 networking including fragmentation and reassembly. In versions before 2025.10, the IPv6 fragmentation reassembly code (specifically the gnrc_ipv6_ext_frag module) contains a classic buffer overflow vulnerability (CWE-120). When processing fragmented IPv6 packets, the system copies the first fragment (offset=0) into a reassembly buffer without verifying that the fragment size fits within the allocated buffer. An attacker can first send a smaller fragment to force the creation of a smaller reassembly buffer, then send a larger fragment to overflow this buffer. This overflow corrupts the state of adjacent packet buffers, which may be leveraged to cause further memory corruption and potentially achieve remote code execution on the device. Exploitation requires no privileges or user interaction but does require the attacker to send crafted IPv6 packets to the device. The vulnerability is mitigated by updating to RIOT-OS version 2025.10, where proper size checks are implemented. No public exploits or widespread attacks have been reported, and the CVSS 4.0 score is 1.7, reflecting low severity due to limited impact and exploitation complexity.

Potential Impact

For European organizations deploying IoT devices running vulnerable versions of RIOT-OS, this vulnerability poses a risk of device compromise through remote code execution. Such devices are often used in critical infrastructure, industrial control systems, smart city applications, and healthcare monitoring, where device integrity and availability are paramount. Exploitation could lead to unauthorized control, data manipulation, or denial of service, potentially disrupting operations or compromising sensitive data. Given the low CVSS score, the immediate risk is limited, but the potential for escalation in complex IoT environments exists. The impact is higher in scenarios where devices are exposed to untrusted IPv6 networks or where network segmentation is weak. European organizations with large IoT deployments should consider this vulnerability seriously, especially in sectors with high reliance on embedded systems.

Mitigation Recommendations

1. Upgrade all RIOT-OS deployments to version 2025.10 or later, where the vulnerability is patched. 2. Disable the gnrc_ipv6_ext_frag module if IPv6 fragmentation is not required in the deployment environment to reduce the attack surface. 3. Implement strict network segmentation and firewall rules to limit exposure of IoT devices to untrusted IPv6 traffic, especially from external networks. 4. Monitor network traffic for anomalous IPv6 fragmentation patterns that could indicate exploitation attempts. 5. Employ intrusion detection systems capable of inspecting IPv6 fragmented packets for suspicious behavior. 6. Conduct regular firmware audits and vulnerability assessments on IoT devices to ensure timely patching and configuration compliance. 7. Collaborate with device manufacturers and vendors to ensure secure update mechanisms are in place for rapid deployment of patches.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-12-05T20:23:19.596Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 6943126ec9138a40d2ed3260

Added to database: 12/17/2025, 8:28:30 PM

Last enriched: 12/24/2025, 8:46:40 PM

Last updated: 2/7/2026, 5:52:30 AM

Views: 47

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats