Skip to content
Fencer Vulns
high 8.6

CVE-2021-38447 json

OCI OpenDDS Secure Amplification

published 2022-05-05 4 y ago modified 2026-06-17 4 mo ago also EUVD-2021-24899

cvss
8.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
2.1%
EPSS 2.1% chance of exploitation in 30 days, percentile 82%
public exploits
0
none known

Summary

OCI OpenDDS versions prior to 3.18.1 are vulnerable when an attacker sends a specially crafted packet to flood target devices with unwanted traffic, which may result in a denial-of-service condition.

Patch / fix

  • OCI OpenDDS 3.18.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-21-315-02 updated cvss 8.6

Multiple Data Distribution Service (DDS) Implementations (Update A)

  • Eclipse CycloneDDS <0.8.0 eProsima Fast DDS <2.4.0 GurumNetworks GurumDDS Object Computing, Inc. (OCI) Object Computing Inc. (OCI) OpenDDS <3.18.1 Real-Time Innovations (RTI) Connext DDS Professional and Connext DDS Secure >=4.2x, <6.1.0 Real-Time Innovations (RTI) RTI Connext DDS Micro >=3.0.0
    +1 more products
    TwinOaks Computing CoreDX DDS <5.9.1
    affected: mitigation “Eclipse recommends users apply the latest CycloneDDS patches.” projects.eclipse.org

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
18 mo ago

Exploit prediction

2.14% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:N/A:P

Affected products

  • OCI OpenDDS

Classification

Weakness
  • CWE-405 Asymmetric Resource Consumption (Amplification)

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.