LiveActive security incident?Get immediate response
CVE Record

CVE-2019-19627: SROS 2 0.8.1 (after CVE-2019-19625 is mitigated) leaks ROS 2 node-related information regardless of the rtp...

SROS 2 0.8.1 (after CVE-2019-19625 is mitigated) leaks ROS 2 node-related information regardless of the rtps_protection_kind configuration. (SROS2 provides the tools to generate and distribute keys for Robot Operating System 2 and uses the underlying security plugins of DDS from ROS 2.)

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 can expose ROS 2 node-related information even when RTPS protection is configured. For organizations using ROS 2 in robotics or automation, this may reveal operational details that security controls were expected to hide. The supplied sources do not show active exploitation or a confirmed fixed version.

Executive priority

Prioritize review if ROS 2 supports production robotics, safety-sensitive automation, or sensitive operational workflows. Treat this as a high-severity exposure concern, but do not assume internet-wide impact or active exploitation from the supplied evidence.

Technical view

The CVE describes an information leak in SROS 2 0.8.1 after CVE-2019-19625 is mitigated. Node-related ROS 2 information is leaked regardless of rtps_protection_kind. SROS2 manages key generation and distribution for ROS 2 and relies on DDS security plugins underneath.

Likely exposure

Exposure is likely limited to environments using SROS 2 0.8.1 with ROS 2/DDS security features. The bundle does not identify downstream products, packaged distributions, or specific deployment defaults beyond SROS 2 0.8.1.

Exploitation context

No CISA KEV listing is provided, and the source bundle does not cite active exploitation. The public references include GitHub issues, a demo recording, workshop material, and a TurtleBot3 demo repository, indicating public technical discussion but not confirmed weaponized exploitation.

Researcher notes

The record is sparse: affected vendor/product fields are n/a, no CWE is listed, and no patch details are included. The key claim is leakage of ROS 2 node-related information independent of rtps_protection_kind after CVE-2019-19625 mitigation.

Mitigation direction

  • Inventory ROS 2 deployments for SROS 2 0.8.1 usage.
  • Review the ROS 2 SROS2 issue for vendor-maintained remediation guidance.
  • Do not rely on rtps_protection_kind to hide node metadata.
  • Restrict ROS 2/DDS exposure to trusted networks where operationally possible.
  • Apply project-provided updates or configuration guidance once confirmed.

Validation and detection

  • Confirm whether SROS 2 0.8.1 is present in robotics environments.
  • Review current rtps_protection_kind assumptions in ROS 2 security profiles.
  • Check whether node metadata is observable from untrusted network positions.
  • Track ROS2/SROS2 project issues for fix status and affected-version clarification.
  • Document any compensating network controls around DDS/ROS 2 traffic.
Prepared
Confidence
medium
Sources
7

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-19627 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
6Source 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-19627Attack 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.