Debian LinuxOperating system · Debian
CVE-2025-62600
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 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.
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 versions prior to 2.6.11, 2.14.6, 3.2.4, 3.3.1, and 3.4.1, an integer overflow vulnerability exists in the readBinaryPropertySeq function when parsing PID_IDENTITY_TOKEN or PID_PERMISSION_TOKEN fields within DATA Submessages of SPDP discovery packets. An attacker can tamper with the length field to trigger an integer overflow, causing excessive memory allocation that leads to Out-of-Memory condition and remote denial of service.
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.
-
Check if Fast DDS is installedLook for Fast DDS libraries or binaries on the system. Common package names include libfastrtps, fast-dds, or eprosima-fast-dds. On Debian systems, check with dpkg -l | grep -i fast or list installed libraries in /usr/lib/Affected if Fast DDS libraries or executables are found on the system
-
Determine the installed Fast DDS versionRun fastdds --version or check the library version. For Debian packages, use dpkg -l | grep -i eprosima-fast-dds. If source-built, check the version.h or CMakeLists.txt in the installation directoryAffected if The version is lower than 2.6.11, 2.14.6, 3.2.4, 3.3.1, or 3.4.1, or falls in the range >= 3.0.0, < 3.3.1, or equals 3.4.0
-
Verify SPDP discovery is enabledCheck the Fast DDS XML configuration file (usually named *.xml in the application directory or /etc/fastdds/) for <discovery> settings. Look for <spdp> tags or the ParticipantDiscoveryProtocol set to SPDPAffected if SPDP discovery protocol is enabled in the Fast DDS configuration
-
Confirm DATA Submessage processing is activeVerify the application initializes DomainParticipants that participate in discovery. This is typically the default behavior for any Fast DDS participant. Check application logs or configuration for DomainParticipant creationAffected if Fast DDS DomainParticipants are running and participating in standard discovery
A system is affected if it runs a vulnerable Fast DDS version with SPDP discovery enabled, which is the default configuration for most Fast DDS deployments.
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. If immediate upgrade is not feasible, implement input validation on the length fields in DATA Submessage processing to reject malformed packets before resize operations.
Upgrade to Fast DDS 2.6.11/2.14.6 (for 2.x users) or 3.3.1/3.4.1 (for 3.x users)
- 1. Identify the currently installed Fast DDS version by checking your project's dependencies or library files
- 2. Determine which major version branch you are using (2.x or 3.x) from your dependency configuration
- 3. For Fast DDS 2.x users: Upgrade to version 2.6.11 or later (or 2.14.6 if using the 2.14 branch)
- 4. For Fast DDS 3.x users: Upgrade to version 3.3.1 or later (or 3.4.1 if using the 3.4 branch)
- 5. Update your package manager or build system to pull the patched version (e.g., conan install fastdds>=2.6.11 or conan install fastdds>=3.3.1)
- 6. Rebuild and recompile your application with the updated Fast DDS library
- 7. Verify the upgrade by checking that the integer overflow vulnerability in readBinaryPropertySeq is no longer present
- 8. Test your application thoroughly, especially security-related functionality using SPDP packets with DATA Submessages
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
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-62600 — 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-62600 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