CVE-2025-62603: CWE-125 Out-of-bounds Read in eProsima Fast-DDS
Fast DDS is a C++ implementation of the DDS (Data Distribution Service) standard of the OMG (Object Management Group ). ParticipantGenericMessage is the DDS Security control-message container that carries not only the handshake but also on going security-control traffic after the handshake, such as crypto-token exchange, rekeying, re-authentication, and token delivery for newly appearing endpoints. On receive, the CDR parser is invoked first and deserializes the `message_data` (i .e., the `DataHolderSeq`) via the `readParticipantGenericMessage → readDataHolderSeq` path. The `DataHolderSeq` is parsed sequentially: a sequence count (`uint32`), and for each DataHolder the `class_id` string (e.g. `DDS:Auth:PKI-DH:1.0+Req`), string properties (a sequence of key/value pairs), and binary properties (a name plus an octet-vector). The parser operat es at a stateless level and does not know higher-layer state (for example, whether the handshake has already completed), s o it fully unfolds the structure before distinguishing legitimate from malformed traffic. Because RTPS permits duplicates, delays, and retransmissions, a receiver must perform at least minimal structural parsing to check identity and sequence n umbers before discarding or processing a message; the current implementation, however, does not "peek" only at a minimal header and instead parses the entire `DataHolderSeq`. As a result, prior to versions 3.4.1, 3.3.1, and 2.6.11, this parsi ng behavior can trigger an out-of-memory condition and remotely terminate the process. Versions 3.4.1, 3.3.1, and 2.6.11 p atch the issue.
AI Analysis
Technical Summary
The vulnerability CVE-2025-62603 resides in eProsima Fast-DDS, a widely used C++ implementation of the OMG DDS standard for real-time data distribution. Fast-DDS uses ParticipantGenericMessage containers to carry DDS Security control messages, including handshake and ongoing security traffic such as crypto-token exchanges and re-authentication. The vulnerability arises during the deserialization process of the message_data field, specifically within the DataHolderSeq sequence. The parser fully unfolds the entire DataHolderSeq structure without performing minimal header checks to validate message legitimacy before parsing. This behavior is problematic because RTPS (Real-Time Publish-Subscribe) protocol allows duplicates, delays, and retransmissions, necessitating at least minimal structural parsing before processing. However, the current implementation parses the entire sequence, which can be malformed or crafted maliciously to cause an out-of-bounds read. This can lead to an out-of-memory condition and remote process termination, effectively causing a denial-of-service (DoS). The vulnerability affects Fast-DDS versions prior to 3.4.1, 3.3.1, and 2.6.11, which have patched this issue. Exploitation requires no authentication or user interaction and can be triggered remotely by sending specially crafted DDS security messages. The CVSS 4.0 score is 1.7, indicating low severity primarily due to limited impact on confidentiality, integrity, and the requirement for specific protocol knowledge to exploit. No known exploits are reported in the wild as of now.
Potential Impact
For European organizations, especially those in sectors relying on real-time data distribution such as industrial automation, automotive, aerospace, and critical infrastructure, this vulnerability poses a risk of denial-of-service through remote process termination. Disruption of Fast-DDS services could impact operational continuity, safety systems, and real-time control processes. Although the vulnerability does not directly compromise confidentiality or integrity, availability impacts could cascade into operational delays or failures. Given the low CVSS score, the immediate risk is limited, but targeted attacks exploiting this flaw could affect high-value systems. The lack of authentication requirements means attackers can attempt exploitation from the network, increasing exposure if DDS traffic is not properly segmented or filtered. European organizations using Fast-DDS in IoT, robotics, or distributed control systems should be particularly vigilant.
Mitigation Recommendations
The primary mitigation is to upgrade eProsima Fast-DDS to versions 3.4.1, 3.3.1, or 2.6.11 or later, where the vulnerability is patched. Organizations should audit their environments to identify Fast-DDS deployments and ensure timely patching. Network-level controls should be implemented to restrict DDS traffic to trusted sources only, employing firewall rules or network segmentation to isolate DDS communication channels. Deploying intrusion detection systems (IDS) or anomaly detection tailored to DDS traffic patterns can help identify malformed or suspicious messages. Additionally, applying rate limiting on DDS security messages may reduce the risk of resource exhaustion. Developers and integrators should review their use of ParticipantGenericMessage parsing to ensure minimal header checks are performed before full deserialization, reducing exposure to malformed inputs. Regular security assessments and penetration testing focusing on DDS implementations can help detect similar vulnerabilities proactively.
Affected Countries
Germany, France, Italy, United Kingdom, Netherlands, Sweden
CVE-2025-62603: CWE-125 Out-of-bounds Read in eProsima Fast-DDS
Description
Fast DDS is a C++ implementation of the DDS (Data Distribution Service) standard of the OMG (Object Management Group ). ParticipantGenericMessage is the DDS Security control-message container that carries not only the handshake but also on going security-control traffic after the handshake, such as crypto-token exchange, rekeying, re-authentication, and token delivery for newly appearing endpoints. On receive, the CDR parser is invoked first and deserializes the `message_data` (i .e., the `DataHolderSeq`) via the `readParticipantGenericMessage → readDataHolderSeq` path. The `DataHolderSeq` is parsed sequentially: a sequence count (`uint32`), and for each DataHolder the `class_id` string (e.g. `DDS:Auth:PKI-DH:1.0+Req`), string properties (a sequence of key/value pairs), and binary properties (a name plus an octet-vector). The parser operat es at a stateless level and does not know higher-layer state (for example, whether the handshake has already completed), s o it fully unfolds the structure before distinguishing legitimate from malformed traffic. Because RTPS permits duplicates, delays, and retransmissions, a receiver must perform at least minimal structural parsing to check identity and sequence n umbers before discarding or processing a message; the current implementation, however, does not "peek" only at a minimal header and instead parses the entire `DataHolderSeq`. As a result, prior to versions 3.4.1, 3.3.1, and 2.6.11, this parsi ng behavior can trigger an out-of-memory condition and remotely terminate the process. Versions 3.4.1, 3.3.1, and 2.6.11 p atch the issue.
AI-Powered Analysis
Technical Analysis
The vulnerability CVE-2025-62603 resides in eProsima Fast-DDS, a widely used C++ implementation of the OMG DDS standard for real-time data distribution. Fast-DDS uses ParticipantGenericMessage containers to carry DDS Security control messages, including handshake and ongoing security traffic such as crypto-token exchanges and re-authentication. The vulnerability arises during the deserialization process of the message_data field, specifically within the DataHolderSeq sequence. The parser fully unfolds the entire DataHolderSeq structure without performing minimal header checks to validate message legitimacy before parsing. This behavior is problematic because RTPS (Real-Time Publish-Subscribe) protocol allows duplicates, delays, and retransmissions, necessitating at least minimal structural parsing before processing. However, the current implementation parses the entire sequence, which can be malformed or crafted maliciously to cause an out-of-bounds read. This can lead to an out-of-memory condition and remote process termination, effectively causing a denial-of-service (DoS). The vulnerability affects Fast-DDS versions prior to 3.4.1, 3.3.1, and 2.6.11, which have patched this issue. Exploitation requires no authentication or user interaction and can be triggered remotely by sending specially crafted DDS security messages. The CVSS 4.0 score is 1.7, indicating low severity primarily due to limited impact on confidentiality, integrity, and the requirement for specific protocol knowledge to exploit. No known exploits are reported in the wild as of now.
Potential Impact
For European organizations, especially those in sectors relying on real-time data distribution such as industrial automation, automotive, aerospace, and critical infrastructure, this vulnerability poses a risk of denial-of-service through remote process termination. Disruption of Fast-DDS services could impact operational continuity, safety systems, and real-time control processes. Although the vulnerability does not directly compromise confidentiality or integrity, availability impacts could cascade into operational delays or failures. Given the low CVSS score, the immediate risk is limited, but targeted attacks exploiting this flaw could affect high-value systems. The lack of authentication requirements means attackers can attempt exploitation from the network, increasing exposure if DDS traffic is not properly segmented or filtered. European organizations using Fast-DDS in IoT, robotics, or distributed control systems should be particularly vigilant.
Mitigation Recommendations
The primary mitigation is to upgrade eProsima Fast-DDS to versions 3.4.1, 3.3.1, or 2.6.11 or later, where the vulnerability is patched. Organizations should audit their environments to identify Fast-DDS deployments and ensure timely patching. Network-level controls should be implemented to restrict DDS traffic to trusted sources only, employing firewall rules or network segmentation to isolate DDS communication channels. Deploying intrusion detection systems (IDS) or anomaly detection tailored to DDS traffic patterns can help identify malformed or suspicious messages. Additionally, applying rate limiting on DDS security messages may reduce the risk of resource exhaustion. Developers and integrators should review their use of ParticipantGenericMessage parsing to ensure minimal header checks are performed before full deserialization, reducing exposure to malformed inputs. Regular security assessments and penetration testing focusing on DDS implementations can help detect similar vulnerabilities proactively.
Affected Countries
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2025-10-16T19:24:37.267Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 69825048f9fa50a62fdc198c
Added to database: 2/3/2026, 7:45:12 PM
Last enriched: 2/3/2026, 8:01:02 PM
Last updated: 2/7/2026, 5:50:57 PM
Views: 15
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2026-2106: Improper Authorization in yeqifu warehouse
MediumCVE-2026-2105: Improper Authorization in yeqifu warehouse
MediumCVE-2026-2090: SQL Injection in SourceCodester Online Class Record System
MediumCVE-2026-2089: SQL Injection in SourceCodester Online Class Record System
MediumCVE-2026-2088: SQL Injection in PHPGurukul Beauty Parlour Management System
MediumActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
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.