CVE-2024-38922: Classic Buffer Overflow
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 11:42 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 47% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 6 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
- Immediately implement strict network segmentation to isolate ROS2 nodes, especially those running nav2_amcl, from untrusted networks and external access.
- Employ message filtering and validation at the network or middleware level to block malformed or unauthorized messages targeting the /initialpose topic.
- Restrict ROS2 communication to authenticated and authorized nodes only, leveraging ROS2 security features such as SROS2 (Secure ROS2) to enforce encryption and access control.
- Monitor ROS2 network traffic for anomalous or unexpected messages that could indicate exploitation attempts.
- Prepare to apply patches or updates from Open Robotics as soon as they become available; track official ROS2 security advisories closely.
- Conduct thorough security reviews of robotic system deployments, including penetration testing focused on ROS2 communication channels.
- Educate operational staff about the risks of accepting messages from untrusted sources and enforce strict operational security policies.
- Consider deploying runtime protection mechanisms or memory safety tools to detect and prevent heap overflow exploitation in robotic software.
Description
Open Robotics Robotic Operating System 2 (ROS2) and Nav2 humble version was discovered to contain a heap overflow in the nav2_amcl process. This vulnerability is triggered via sending a crafted message to the component /initialpose.