dbcve.org
Dds SecurityApplication · Omg

CVE-2019-15135

HIGH · 7.5 CVSS v3.0 Published 2019-08-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
The handshake protocol in Object Management Group (OMG) DDS Security 1.1 sends cleartext information about all of the capabilities of a participant (including capabilities inapplicable to the current session), which makes it easier for attackers to discover potentially sensitive reachability information on a Data Distribution Service (DDS) network.

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

The handshake protocol in OMG DDS Security 1.1 transmits cleartext information about all participant capabilities during session establishment, including capabilities not applicable to the current session. This exposes sensitive reachability information about DDS network participants to potential attackers on the network.

MitigationRestrict the handshake protocol to exchange only capabilities relevant to the current session and/or encrypt handshake messages to prevent disclosure of reachability information.

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
Dds SecurityApplication
Affected:= 1.1

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
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

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

  1. Confirm DDS Security version 1.1 is in use
    Identify the installed DDS Security library/plugin version by checking your software bill of materials, dependency list, or the shared libraries loaded by your DDS application. Compare the version to 1.1.
    Affected if The DDS Security implementation version is exactly 1.1
  2. Verify DDS Security plugins are enabled
    Check your DDS DomainParticipant configuration or application code to confirm that security plugins (Authentication, AccessControl, and/or Cryptographic) are enabled. This is typically done via the property QosPolicy with plugin-specific property names.
    Affected if DDS Security plugins are enabled and the version is 1.1
  3. Capture participant handshake traffic
    Use a network packet capture tool (such as tcpdump or Wireshark) to capture RTPS (Real-Time Publish-Subscribe) protocol traffic on the DDS discovery multicast or unicast ports when a new participant joins the domain.
    Affected if DDS Security 1.1 is in use with security plugins enabled and participants are joining the domain
  4. Inspect handshake messages for cleartext capabilities
    Examine the captured RTPS packets during the participant handshake phase. Look for ParticipantStatelessMessage or ParticipantVolatileMessageSecure sub-messages that contain capability information. Verify whether these capability data elements are transmitted in cleartext (unencrypted).
    Affected if The handshake messages contain cleartext capability information about participants beyond those relevant to the current session

You are affected if you are using OMG DDS Security version 1.1 with security plugins enabled and your network captures show unencrypted capability information being exchanged during participant handshake.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict the handshake protocol to exchange only capabilities relevant to the current session and/or encrypt handshake messages to prevent disclosure of reachability information.

Fix this in Dds Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-15135 — 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-2019-15135 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