CVE-2023-50716
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 (formerly Fast RTPS) is a C++ implementation of the Data Distribution Service standard of the Object Management Group. Prior to versions 2.13.0, 2.12.2, 2.11.3, 2.10.3, and 2.6.7, an invalid DATA_FRAG Submessage causes a bad-free error, and the Fast-DDS process can be remotely terminated. If an invalid Data_Frag packet is sent, the `Inline_qos, SerializedPayload` member of object `ch` will attempt to release memory without initialization, resulting in a 'bad-free' error. Versions 2.13.0, 2.12.2, 2.11.3, 2.10.2, and 2.6.7 fix this issue.
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.13.0, 2.12.2, 2.11.3, 2.10.3, and 2.6.7, an invalid DATA_FRAG Submessage triggers a bad-free error. Specifically, when an invalid Data_Frag packet is received, the Inline_qos and SerializedPayload members of the ch object attempt to release uninitialized memory, causing the Fast-DDS process to crash remotely.
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< 2.6.7>= 2.10.0, < 2.10.3>= 2.11.0, < 2.11.3>= 2.12.0, < 2.12.2CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 if eProsima Fast DDS is installedCheck for Fast DDS libraries or binaries: locate libfastrtps.so, fastdds executable, or inspect running processes for fastdds/fast-rtps related names. On Linux: 'ldconfig -p | grep fastrtps' or 'ps aux | grep -i dds'Affected if Fast DDS libraries or processes are found on the system
-
Determine the installed Fast DDS versionQuery the library version: run 'ldconfig -p | grep fastrtps' to find the library path, then check the file version with 'strings <library_path> | grep -i version' or check the product documentation. If running as a service, check the service version with 'dpkg -l | grep fast-dds' or 'rpm -qa | grep fast-dds'Affected if The version cannot be determined or is found within the affected ranges (< 2.6.7, 2.10.0-2.10.2, 2.11.0-2.11.2, or 2.12.0-2.12.1)
-
Compare your version against affected rangesParse the version number identified in step 2. Affected ranges: < 2.6.7; >= 2.10.0 and < 2.10.3; >= 2.11.0 and < 2.11.3; >= 2.12.0 and < 2.12.2Affected if Your installed version falls into any of these ranges: < 2.6.7, 2.10.0-2.10.2, 2.11.0-2.11.2, or 2.12.0-2.12.1
-
Check network exposure of Fast DDS serviceIdentify if Fast DDS is listening on network ports. Run 'netstat -tulpn | grep -E "7400|fastdds"' or 'ss -tulpn' to find listening ports. Fast DDS typically uses port 7400 by default but may be configured differentlyAffected if Fast DDS is listening on accessible network ports, especially if exposed to untrusted participants
You are affected if Fast DDS is installed with a version in the ranges < 2.6.7, 2.10.0-2.10.2, 2.11.0-2.11.2, or 2.12.0-2.12.1 and the service is network-accessible to untrusted participants.
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.72.10.32.11.3
Upgrade eProsima Fast DDS to versions 2.13.0, 2.12.2, 2.11.3, 2.10.3, or 2.6.7 or later. If immediate upgrade is not feasible, consider network segmentation to limit exposure to untrusted DDS participants.
Fast DDS 2.13.0 (latest stable release, contains all security fixes)
- 1. Identify the current Fast DDS version in use by checking the project's dependency files or library version
- 2. Download the appropriate fixed release for your current major version branch
- 3. For Fast DDS < 2.6.7: upgrade to version 2.6.7
- 4. For Fast DDS >= 2.10.0 and < 2.10.3: upgrade to version 2.10.3
- 5. For Fast DDS >= 2.11.0 and < 2.11.3: upgrade to version 2.11.3
- 6. For Fast DDS >= 2.12.0 and < 2.12.2: upgrade to version 2.12.2
- 7. Recompile any applications that statically link against Fast DDS
- 8. Test the application to ensure the upgrade does not break existing functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50716 — 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-2023-50716 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