Debian LinuxOperating system · Debian
CVE-2025-62599
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedeprosima 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 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 readPropertySeq — 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn eprosima Fast DDS, an integer overflow vulnerability exists in the security module when parsing DATA Submessages within SPDP (Simple Participant Discovery Protocol) packets. By tampering with the length field in readPropertySeq for PID_IDENTITY_TOKEN or PID_PERMISSION_TOKEN, an attacker can trigger excessive memory allocation, causing an Out-Of-Memory condition that terminates the Fast-DDS process.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Debian LinuxOperating system
= 11.0= 12.0= 13.0< 2.6.11>= 3.0.0, < 3.3.1= 3.4.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Fast DDS versionRun 'dpkg -l | grep fast-dds' on Debian systems, or check the library file version using 'ldd' on the compiled binary and look for libfastdds.so version, or examine build manifests if statically linkedAffected if The installed version is less than 2.6.11, or between 3.0.0 and 3.3.1 inclusive, or exactly 3.4.0
-
Verify if security module is enabledExamine the Fast DDS XML configuration file (typically in /etc/fastdds.xml or a local .xml file) for the <security> tag, or check the participant Qos profile for Security.enabled set to trueAffected if The security plugin (DDS-Security) is enabled in the participant configuration, as the vulnerability exists in the security module's DATA Submessage parsing
-
Confirm SPDP discovery protocol is in useReview the participant configuration for <discovery> settings; check if SimpleParticipantDiscoveryProtocol (SPDP) is explicitly configured or is the default, and look for related participant discovery endpoints in network trafficAffected if SPDP is being used for participant discovery, as the vulnerability is triggered specifically during SPDP packet parsing
A system is affected if it runs a vulnerable Fast DDS version (below 2.6.11, between 3.0.0-3.3.1, or exactly 3.4.0) with the security module enabled and SPDP discovery protocol in use.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.6.113.3.1
Upgrade Fast DDS to version 2.6.11, 2.14.6, 3.2.4, 3.3.1, or 3.4.1 (or later) to patch the integer overflow vulnerability in the security module's DATA Submessage parsing.
Upgrade to Fast DDS 2.14.6 (for 2.x users) or 3.4.1 (for 3.x users)
- 1. Identify the current Fast DDS version in use by checking project dependencies or library version
- 2. Determine which version branch is currently installed (2.x, 3.0.x-3.2.x, or 3.3.x-3.4.0)
- 3. For Debian Linux systems, check if the distribution has packaged the fixed version via: apt-cache policy libfast-dds-dev or apt list --installed | grep fast-dds
- 4. For source-based installations, obtain the fixed version from the eprosima Fast DDS GitHub repository releases
- 5. If on Fast DDS 2.x versions below 2.6.11, upgrade to version 2.14.6 (latest 2.x stable with fix)
- 6. If on Fast DDS 3.0.x through 3.2.x, upgrade to version 3.3.1 or 3.4.1
- 7. If on Fast DDS 3.4.0, upgrade to version 3.4.1
- 8. Rebuild and redeploy the application with the new Fast DDS library
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62599 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-62599 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data