dbcve.org
Debian LinuxOperating system · Debian

CVE-2023-39948

HIGH · 7.5 CVSS v3.1 Published 2023-08-11
Fix available
A fix is available. Upgrade to 2.6.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
eprosima Fast DDS is a C++ implementation of the Data Distribution Service standard of the Object Management Group. Prior to versions 2.10.0 and 2.6.5, the `BadParamException` thrown by Fast CDR is not caught in Fast DDS. This can remotely crash any Fast DDS process. Versions 2.10.0 and 2.6.5 contain a patch for 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 confidence

Fast DDS fails to catch BadParamException thrown by Fast CDR during serialization operations. This unhandled exception causes Fast DDS processes to crash when malformed data is received, leading to denial of service.

MitigationUpgrade Fast DDS to version 2.10.0 or 2.6.5 (depending on the release branch in use) to include the exception handling patch.

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
Affected:= 11.0= 12.0
Fast DdsApplication
Affected:>= 2.6.0, < 2.6.5= 2.10.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Fast DDS is installed
    On Debian systems, run 'dpkg -l | grep -i fast-dds' or 'apt list --installed 2>/dev/null | grep -i fast-dds' to list installed Fast DDS packages
    Affected if No Fast DDS package is found in the package listing
  2. Determine the installed Fast DDS version
    Run 'dpkg -l <fast-dds-package-name>' replacing <fast-dds-package-name> with the package found in step 1, or use 'apt show <package-name>' to display version details
    Affected if The displayed version matches '2.6.0' through '2.6.4', or shows exactly '2.10.0'
  3. Check for Fast DDS shared libraries
    Search for Fast DDS library files using 'find /usr -name "*fastdds*" -o -name "*fast-rtps*" 2>/dev/null' to locate installed library components
    Affected if Fast DDS libraries are found on the system and the version cannot be determined via package manager
  4. Verify the Fast CDR dependency version
    Check installed Fast CDR library version with 'dpkg -l | grep -i fast-cdr' or by inspecting the library linked to any Fast DDS applications via 'ldd <application> | grep -i fast'
    Affected if Fast CDR version is found but Fast DDS version remains in the affected range

A system is affected if Fast DDS version 2.6.0 through 2.6.4 or exactly version 2.10.0 is installed, or if Fast DDS libraries are present without clear version information on Debian 11 or 12.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.6.5 or later
Fixed in 2.6.5
Interim mitigation

Upgrade Fast DDS to version 2.10.0 or 2.6.5 (depending on the release branch in use) to include the exception handling patch.

Recommended fix High confidence

Upgrade to Fast DDS version 2.10.0 (or 2.6.5 for the 2.6.x branch)

  1. 1. Identify the current Fast DDS version in use by checking project dependencies or running `fastdds --version`
  2. 2. For Debian systems: Run `apt update` and `apt upgrade` to get the latest security updates for the fastdds packages
  3. 3. For C++ projects using Fast DDS: Update the dependency in your build system (CMake, conan, vcpkg, etc.) to version 2.6.5 or 2.10.0
  4. 4. Rebuild and test the application to ensure the upgrade does not introduce regressions
  5. 5. Verify the new version is running: confirm the BadParamException is now properly caught and handled

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing8.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,140
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-39948 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-39948 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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