Unsafe eval() in Open Source Robotics Foundation Robot Operating System rosparam enables arbitrary code execution

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2024-39289?

CVE-2024-39289 is a vulnerability classified as Improper Neutralization of Directives in Dynamically Evaluated Code and Improper Control of Generation of Code, affecting Robot Operating System (ROS) (affected versions: Noetic Ninjemys, Melodic Morenia, and other affected versions). This vulnerability is rated High, with a CVSS score of 7.8. Current sources do not report this vulnerability as exploited.

Overview

Original source data

A code execution vulnerability has been discovered in the Robot Operating System (ROS) 'rosparam' tool, affecting ROS distributions Noetic Ninjemys and earlier. The vulnerability stems from the use of the eval() function to process unsanitized, user-supplied parameter values via special converters for angle representations in radians. This flaw allowed attackers to craft and execute arbitrary Python code.

Affected products and scope

  • Open Source Robotics Foundation Robot Operating System (ROS), package rosparam, is recorded as affected in the Noetic Ninjemys, Melodic Morenia, Kinetic Kame, and Indigo Igloo distributions.
  • The CNA record identifies Linux, Windows, and MacOS platforms.
  • default_status is set to unaffected, while the branches listed above have explicit affected status.
  • No exact patched release or branch-specific fixed boundary is supplied. The safety of other branches must not be inferred solely from their omission from the affected list.

Technical details

The flaw is in the rosparam tool of Robot Operating System (ROS), where eval() processes user-supplied parameter values without sanitization. The processing path involves special converters for angle representations in radians. Crafted values can cause the tool to execute arbitrary Python code, matching CWE-95 and CWE-94. The record describes local reachability, no required privileges, low complexity, and required user interaction. It does not identify the exact function, converter name, or complete call path, so those implementation details remain unknown.

Exploitability

The vulnerability is described as locally reachable rather than as a network service that can be directly exploited remotely. The record indicates that no privileges are required and that complexity is low, but user interaction is required, meaning a user or process must handle a crafted parameter value. The exact workflow for supplying that value to rosparam is not documented in the record. The supplied record marks public_exploit as false, and the CISA ADP enrichment records exploitation as none in the available data. These statuses do not guarantee that abuse cannot occur in a particular environment.

Technical impact

The direct technical outcome is arbitrary Python code execution in the process that handles the parameter value. The record describes high confidentiality, integrity, and availability consequences, while scope remains within the same security authority. Because user interaction is required, exploitation depends on getting a user or process to handle crafted data. Organisational consequences may include configuration changes, access to data available to the process, or service disruption, depending on process privileges and system isolation.

Business impact

Successful exploitation can execute arbitrary Python code in the context of the process running rosparam. Depending on that process's permissions and accessible resources, an attacker could read data, modify configuration, or disrupt the tool and related ROS workloads. In robotics environments, changes to parameters or supporting processes could affect system stability, but the actual consequences depend on deployment permissions and isolation. The record does not confirm a specific incident, victim, or data breach.

Remediation

  1. Migrate from ROS (1) versions that are end of life to a ROS 2 version, following the solution stated in the record.
  2. Do not treat an upgrade to another ROS (1) release as a confirmed fix, because the data does not identify a specific fixed ROS (1) release.
  3. Until migration is complete, avoid feeding untrusted parameter values into workflows that use the affected angle converters for radians. This is a risk-reduction measure based on the described mechanism, not a confirmed vendor patch.
  4. After migration, verify that no affected branch remains and that no legacy workflow still depends on rosparam.

Detection

  1. Inventory hosts and images running ROS on Linux, Windows, or MacOS, then identify installed instances of the rosparam package and tool.
  2. Compare each ROS distribution with the affected branches listed in affected_summary.
  3. Review scripts, pipelines, and configuration sources that can supply user-controlled or untrusted parameter values to angle representation converters using radians.
  4. After migration or removal, repeat the inventory to confirm that no legacy ROS instance still uses the affected rosparam workflow.
  5. Process telemetry and unusual child activity around tool execution may be reviewed as precautionary monitoring. The record provides no specific IOC or log signature, so the absence of suspicious logs does not prove that a system is safe.
Sources (15)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.