LiveActive security incident?Get immediate response
CVE Record

CVE-2020-10289: RVD#2401: Use of unsafe yaml load, ./src/actionlib/tools/library.py:132

Use of unsafe yaml load. Allows instantiation of arbitrary objects. The flaw itself is caused by an unsafe parsing of YAML values which happens whenever an action message is processed to be sent, and allows for the creation of Python objects. Through this flaw in the ROS core package of actionlib, an attacker with local or remote access can make the ROS Master, execute arbitrary code in Python form. Consider yaml.safe_load() instead. Located first in actionlib/tools/library.py:132. See links for more info on the bug.

HighCVSS 8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This vulnerability affects ROS actionlib in ROS Melodic Morenia and earlier. Unsafe YAML parsing can create Python objects during action message handling, which the public record says could let an attacker with local or remote access make ROS Master execute arbitrary Python code.

Executive priority

Treat this as high priority for robotics environments because impact is full confidentiality, integrity, and availability compromise, but prioritize based on whether vulnerable ROS systems are reachable by untrusted users.

Technical view

CVE-2020-10289 is unsafe YAML loading in actionlib/tools/library.py around line 132. The issue occurs when action messages are processed for sending. CVSS 3.0 is 8.0 with network attack vector, low complexity, low privileges required, and user interaction required.

Likely exposure

Organizations using Open Robotics ROS Melodic Morenia or earlier distributions with actionlib are potentially exposed, especially where ROS Master or related ROS communication is reachable by untrusted local or remote users.

Exploitation context

The source bundle does not show CISA KEV listing or confirmed active exploitation. The CVSS vector indicates network reachability, low attack complexity, low privileges, and required user interaction.

Researcher notes

Evidence is limited to the CVE record and the linked actionlib pull request. The record identifies unsafe YAML parsing, affected ROS versions, and a safe_load direction, but does not provide confirmed exploitation or package-level fixed version data.

Mitigation direction

  • Upgrade ROS/actionlib to a vendor-fixed release if available.
  • Review the linked actionlib pull request and vendor guidance before patching.
  • Replace unsafe YAML loading with safe loading in maintained forks.
  • Restrict ROS Master access to trusted hosts and users.
  • Avoid exposing ROS communication paths to untrusted networks.

Validation and detection

  • Inventory ROS distributions and actionlib versions in use.
  • Check whether systems run ROS Melodic Morenia or earlier.
  • Inspect actionlib/tools/library.py for unsafe yaml.load usage.
  • Verify whether the fix from actionlib PR 171 is present.
  • Review network access paths to ROS Master.
Prepared
Confidence
medium
Sources
3

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.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-10289 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
8 (3.0)
Known Exploited
No
Published

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

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
2Source 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
8CVSS 3.0HighCVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H2.15.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.0 score

8High
CVSS 3.0 vector shape for CVE-2020-10289Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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
Open RoboticsrosROS Melodic Morenia and prior distrosListed
Weakness

CWE details

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

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.