CVE-2025-67108
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 v3.3 was discovered to contain improper validation for ticket revocation, resulting in insecure communications and connections.
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 · moderate confidenceeProsima Fast-DDS v3.3 has improper validation for ticket revocation, allowing authentication tokens that should have been revoked to remain valid. This enables attackers to maintain insecure communications and establish unauthorized connections to DDS domains.
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= 3.3.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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N
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 'pip show fast-dds' or check the library binary version. On Linux: 'ldd <your_binary> | grep fastdds' or check '/usr/lib/x86_64-linux-gnu/libfastdds.so.3.3.0'. In CMake projects, check the version.h or version.cmake file.Affected if The installed version is exactly 3.3.0
-
Confirm Authentication plugin is enabledReview your Fast-DDS XML configuration files (typically *.xml) for <plugin> or <security> sections. Look for 'Authentication' or 'participant' configuration with security properties enabled. Check if ParticipantPropertyPartition includes security-related settings.Affected if Authentication plugin is configured and enabled in your deployment
-
Inspect active DDS participants and connectionsUse Fast-DDS discovery tool or monitor your DDS domain. Run 'fastdds discovery' or equivalent domain monitor to list all active participants in your domain. Check for unexpected participants or duplicate identities.Affected if There are participants in your DDS domain that should not be present or that you do not recognize
-
Review security event logs for ticket validationExamine Fast-DDS logs with debug/security level enabled. Search for 'authentication', 'ticket', 'revoke', or 'validation' messages. Check if any recently revoked tickets are still being accepted.Affected if Logs show tickets marked as revoked are still being validated as valid or accepted for new connections
You are affected if running Fast-DDS version 3.3.0 with authentication enabled and there are active connections using tickets that should have been revoked.
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.
From vendor dataUpgrade to a patched version of eProsima Fast-DDS that properly validates and revokes tickets. Review existing deployments for evidence of compromise using revoked credentials.
- 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-67108 — 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-67108 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