Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-38921: n/a

0
Critical
VulnerabilityCVE-2024-38921cvecve-2024-38921
Published: Fri Dec 06 2024 (12/06/2024, 00:00:00 UTC)
Source: CVE Database V5

Description

Open Robotics Robotic Operating System 2 (ROS2) and Nav2 humble versions were discovered to contain a use-after-free via the nav2_amcl process. This vulnerability is triggered via remotely sending a request for change the value of dynamic-parameter`/amcl z_rand ` .

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/28/2026, 04:07:08 UTC

Technical Analysis

CVE-2024-38921 identifies a critical use-after-free vulnerability in the nav2_amcl process of the Open Robotics Robotic Operating System 2 (ROS2) and Nav2 humble versions. The vulnerability arises when a remote attacker sends a specially crafted request to change the dynamic parameter `/amcl z_rand`, which is used in the adaptive Monte Carlo localization (AMCL) component responsible for robot localization. This use-after-free condition (CWE-416) can lead to memory corruption, enabling remote code execution, denial of service, or unauthorized control over the robotic system. The vulnerability requires no privileges or user interaction, making it remotely exploitable over the network (CVSS vector: AV:N/AC:L/PR:N/UI:N). ROS2 is widely used in robotics research, industrial automation, and autonomous systems, making this vulnerability particularly impactful. The lack of available patches at the time of publication increases the urgency for mitigations. The vulnerability affects all deployments using the vulnerable Nav2 humble versions and the AMCL node, which is a core component for navigation stacks. Given the critical nature of the flaw and the high CVSS score of 9.8, it represents a severe threat to the confidentiality, integrity, and availability of robotic systems.

Potential Impact

The exploitation of CVE-2024-38921 can have severe consequences for organizations relying on ROS2-based robotic systems. Successful attacks can lead to arbitrary code execution, allowing attackers to take full control of affected robots, manipulate navigation and localization data, or disrupt operations through denial of service. This can result in physical damage, safety hazards, operational downtime, and loss of sensitive data. Industries such as manufacturing, logistics, healthcare, and defense that increasingly depend on autonomous robots are particularly vulnerable. The remote and unauthenticated nature of the exploit increases the attack surface, potentially allowing attackers to compromise systems from external networks. The impact extends beyond individual robots to entire robotic fleets or automated processes, amplifying operational risks and financial losses. Additionally, compromised robots could be used as pivot points for lateral movement within enterprise networks, further escalating the threat.

Mitigation Recommendations

To mitigate CVE-2024-38921, organizations should immediately implement network segmentation and restrict access to ROS2 nodes, especially the nav2_amcl process and its dynamic parameter interfaces. Employ strict firewall rules and access controls to limit who can send parameter change requests. Monitor network traffic for anomalous or unauthorized parameter modification attempts. Until official patches are released, consider disabling or isolating the AMCL node if feasible, or deploying additional runtime protections such as memory safety tools or intrusion detection systems tailored for ROS2 environments. Conduct thorough security assessments of robotic systems and update incident response plans to include potential exploitation scenarios. Engage with the ROS2 community and vendors for timely updates and patches. Additionally, implement robust authentication and authorization mechanisms for dynamic parameter changes to prevent unauthorized access. Regularly audit and update robotic software dependencies to minimize exposure to known vulnerabilities.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
mitre
Date Reserved
2024-06-21T00:00:00.000Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 699f6c7cb7ef31ef0b564f66

Added to database: 2/25/2026, 9:41:16 PM

Last enriched: 2/28/2026, 4:07:08 AM

Last updated: 4/12/2026, 12:46:05 AM

Views: 16

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses