CVE-2025-62600
Memory Safety in Eprosima Fast Dds ≤ 2.6.11
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:HSummary
CVE-2025-62600 is a high-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Eprosima Fast Dds. Its CVSS base score is 8.6 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-62600 affects eProsima Fast DDS, a C++ implementation of the OMG Data Distribution Service (DDS) standard. In versions prior to 2.6.11, 2.14.6, 3.2.4, 3.3.1, and 3.4.1, the vulnerability arises when security mode is enabled and an attacker modifies the DATA Submessage within an SPDP packet sent by a publisher. Specifically, tampering with the length field in the readBinaryPropertySeq function for PID_IDENTITY_TOKEN or PID_PERMISSION_TOKEN fields triggers an integer overflow (CWE-190), leading to an out-of-memory (OOM) condition (CWE-789) during a resize operation. This results in remote termination of the Fast DDS process. The issue carries a CVSS v3.1 base score of 8.6 (AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H).
A remote, unauthenticated attacker can exploit this vulnerability by crafting and sending a tampered SPDP packet over the network to a targeted Fast DDS instance with security enabled. No user interaction is required, and the attack has low complexity. Successful exploitation causes an OOM denial-of-service, terminating the affected process and potentially disrupting DDS-based communications in real-time systems.
The vulnerability is addressed in Fast DDS versions 2.6.11, 2.14.6, 3.2.4, 3.3.1, and 3.4.1, as detailed in the eProsima security advisory at https://github.com/eProsima/Fast-DDS/security/advisories/GHSA-hvm8-mm7f-m6hc. Security practitioners should upgrade to a patched version to mitigate the risk.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-206677
Vulnerability Data
eprosima Fast DDS is a C++ implementation of the DDS (Data Distribution Service) standard of the OMG (Object Management Group). Prior to 2.6.11, 2.14.6, 3.2.4, 3.3.1, and 3.4.1, when the security mode is enabled, modifying the DATA Submessage within an…
more
SPDP packet sent by a publisher causes an Out-Of-Memory (OOM) condition, resulting in remote termination of Fast-DDS. If the fields of PID_IDENTITY_TOKEN or PID_PERMISSION_TOKEN in the DATA Submessage — specifically by tampering with the length field in readBinaryPropertySeq— are modified, an integer overflow occurs, leading to an OOM during the resize operation. This vulnerability is fixed in 2.6.11, 2.14.6, 3.2.4, 3.3.1, and 3.4.1.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.2.6
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds integer overflow defects before deployment.
Input validation directly rejects or bounds untrusted size values before any allocation occurs.
Secure engineering principles require use of safe arithmetic constructs or language features that structurally eliminate integer overflow during calculation.
Resource quotas and priority allocation limit the system-wide impact of an oversized request.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development can detect integer overflows before release.
Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.
Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.
Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.
Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.
Capacity management monitors overall resource use but does not prevent individual allocation bugs.