LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19625: SROS 2 0.8.1 (which provides the tools that generate and distribute keys for Robot Operating System 2 and u...

SROS 2 0.8.1 (which provides the tools that generate and distribute keys for Robot Operating System 2 and uses the underlying security plugins of DDS from ROS 2) leaks node information due to a leaky default configuration as indicated in the policy/defaults/dds/governance.xml document.

HighCVSS 7.5Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

SROS 2 0.8.1 used insecure default security policy settings that could expose ROS 2 node information. For robotics environments, this may reveal operational topology or components to an unauthenticated network observer. The sources do not show active exploitation or identify a specific fixed release.

Executive priority

Treat this as a high-priority robotics security hygiene issue where ROS 2 networks are reachable. It may expose system topology that helps attackers plan later activity, but the provided sources do not show active exploitation or direct system takeover.

Technical view

CVE-2019-19625 concerns a leaky default configuration in SROS 2 0.8.1, specifically policy/defaults/dds/governance.xml. SROS 2 generates and distributes keys for ROS 2 and relies on DDS security plugins. The CVSS vector is network-reachable, low complexity, unauthenticated, and no user interaction.

Likely exposure

Exposure is most likely where SROS 2 0.8.1 generated ROS 2/DDS security artifacts are deployed on reachable robot or automation networks. The source bundle does not identify CPEs or broader affected versions.

Exploitation context

The bundle marks KEV as false and provides no cited evidence of active exploitation. The risk is information leakage from default configuration, not a documented remote code execution path.

Researcher notes

The CVE text and references are sparse. Key unknowns include exact affected version range, merge status of the upstream PR, and whether downstream ROS 2 distributions backported changes. Validate against source configuration and vendor guidance.

Mitigation direction

  • Inventory ROS 2 environments using SROS 2 0.8.1-generated security artifacts.
  • Review vendor or upstream SROS 2 guidance before changing DDS security policy defaults.
  • Assess the upstream pull request reference for the intended configuration correction.
  • Limit ROS 2/DDS network exposure to trusted operational networks.
  • Regenerate and redeploy security artifacts only after validating approved configuration changes.

Validation and detection

  • Confirm whether policy/defaults/dds/governance.xml defaults are present in deployed artifacts.
  • Verify whether node information is exposed in a controlled, authorized test environment.
  • Check SROS 2 version and provenance for generated key material.
  • Document ROS 2/DDS network boundaries and unauthenticated reachability.
  • Record whether upstream PR 171 or vendor guidance has been applied.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2019-19625 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.0)
Known Exploited
No
Published

Vector: CVSS:3.0/AC:L/AV:N/A:H/C:N/I:N/PR:N/S:U/UI:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.0HighCVSS:3.0/AC:L/AV:N/A:H/C:N/I:N/PR:N/S:U/UI:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

7.5High
CVSS 3.0 vector shape for CVE-2019-19625Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.0/AC:L/AV:N/A:H/C:N/I:N/PR:N/S:U/UI:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.