CVE-2025-62602
Heap Buffer Overflow in Fast DDS SPDP Packet Causes Remote DoS
Publication date: 2026-02-03
Last updated on: 2026-02-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| eprosima | fast_dds | to 2.6.11 (exc) |
| eprosima | fast_dds | From 3.0.0 (inc) to 3.3.1 (exc) |
| eprosima | fast_dds | 3.4.0 |
| debian | debian_linux | 11.0 |
| debian | debian_linux | 12.0 |
| debian | debian_linux | 13.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-122 | A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-62602 is a vulnerability in Fast DDS, a C++ implementation of the Data Distribution Service standard. When security mode is enabled, an attacker can modify the DATA Submessage within an SPDP packet sent by a publisher to cause a heap buffer overflow. Specifically, tampering with the PID_IDENTITY_TOKEN or PID_PERMISSIONS_TOKEN fields leads to an unchecked vector size that triggers a 32-bit integer overflow during length calculation. This overflow causes a large memory allocation attempt that results in out-of-memory conditions, enabling remote denial-of-service and process termination.
How can this vulnerability impact me? :
This vulnerability can allow a remote attacker to cause a denial-of-service by triggering a heap buffer overflow and out-of-memory condition in Fast DDS. The result is remote termination of the Fast DDS process, which can disrupt applications relying on this middleware for data distribution.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, upgrade Fast DDS to version 3.4.1 or later, where the issue has been fixed.
If you are using Debian packages, note that no fixed versions are currently released in Debian unstable, so consider applying the upstream patch available at the GitHub repository.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided information does not specify how this vulnerability affects compliance with common standards and regulations such as GDPR or HIPAA.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability affects specific versions of Fast DDS prior to 3.4.1, 3.3.1, and 2.6.11. Detection involves identifying if these vulnerable versions are running on your system.
You can check the installed Fast DDS version using package management or by querying the software directly. For example, on Debian-based systems, you can use:
- dpkg -l | grep fast-dds
- apt-cache policy fast-dds
Since the vulnerability is triggered by malformed SPDP packets with tampered DATA Submessages, network detection could involve monitoring DDS traffic for unusual or malformed SPDP packets, especially those containing manipulated PID_IDENTITY_TOKEN or PID_PERMISSIONS_TOKEN fields. However, no specific detection commands or signatures are provided in the available resources.