CVE-2024-25199: Use After Free
Source CVE Database V5
Not known to be exploited · CVSS 8.1 High.
Data as of 26 Oct 2026, 17:16 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:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 20 Feb 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
- Monitor Open Robotics and Nav2 project repositories for official patches addressing CVE-2024-25199 and apply updates promptly once available.
- Until patches are released, restrict network access to ROS2 nodes, especially limiting access to trusted hosts within secure network segments to reduce exposure to adjacent attackers.
- Employ runtime memory protection mechanisms such as AddressSanitizer or similar tools during development and testing phases to detect use-after-free conditions early.
- Conduct thorough code reviews focusing on pointer management and lifecycle in amcl_node.cpp and related modules to identify and remediate unsafe memory handling.
- Implement network segmentation and firewall rules to isolate robotic systems from untrusted networks and reduce attack surface.
- Use containerization or sandboxing techniques for ROS2 nodes to limit impact of potential exploitation.
- Maintain comprehensive logging and monitoring to detect anomalous behavior or crashes indicative of exploitation attempts.
- Educate development teams on secure coding practices related to memory management in C++ to prevent similar vulnerabilities.
Description
Inappropriate pointer order of map_sub_ and map_free(map_) (amcl_node.cpp) in Open Robotics Robotic Operating Sytstem 2 (ROS2) and Nav2 humble versions leads to a use-after-free.