Skip to main content
VulnerabilityPublished Updated

CVE-2024-37863: Classic Buffer Overflow

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Dec 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

Given the absence of official patches, organizations should implement the following specific mitigations: 1) Restrict network access to the nav2_amcl process by enforcing strict firewall rules and network segmentation to limit exposure to untrusted sources. 2) Employ application-layer filtering or input validation proxies to detect and block malformed or suspicious .yaml files before they reach the vulnerable process. 3) Monitor ROS2 and Nav2 humble deployments for unusual activity or crashes indicative of exploitation attempts. 4) Use containerization or sandboxing techniques to isolate the nav2_amcl process, limiting the impact of potential exploitation. 5) Engage with the ROS2 community and Open Robotics for timely updates and patches, and plan rapid deployment once available. 6) Conduct code audits and fuzz testing on .yaml file parsing components to identify and remediate similar vulnerabilities proactively. 7) Implement robust logging and alerting mechanisms to detect exploitation attempts early. These targeted measures go beyond generic advice by focusing on network controls, input validation, process isolation, and proactive vulnerability management tailored to the ROS2 environment.

Description

Open Robotics Robotic Operating System 2 (ROS2) and Nav2 humble versions were discovered to contain a buffer overflow via the nav2_amcl process. This vulnerability is triggered via sending a crafted .yaml file.

References

Community reviews

Loading reviews…