dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-37862

HIGH · 7.3 CVSS v3.1 Published 2024-12-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
73/100
Remediation priority · Elevated

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Buffer Overflow vulnerability in Open Robotic Robotic Operating System 2 ROS2 navigation2- ROS2-humble&& navigation2-humble allows a local attacker to execute arbitrary code via a crafted .yaml file to the nav2_planner process.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A buffer overflow vulnerability exists in the nav2_planner component of ROS2 Humble's navigation2 package. The vulnerability is triggered when the nav2_planner process parses a maliciously crafted .yaml configuration file, allowing a local attacker to overflow a buffer and execute arbitrary code.

MitigationImplement strict input validation and bounds checking on YAML configuration file parsing in nav2_planner, specifically validating buffer lengths before copying data from parsed YAML content. Consider using safe YAML parsing libraries that prevent buffer overflows.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify navigation2 package version
    Run 'ros2 pkg list | grep navigation2' to list the navigation2 package, then check the installed version with 'ros2 pkg prefix navigation2' and inspect the package.xml or check via 'dpkg -l | grep ros-humble-navigation2' or 'apt list --installed | grep navigation2'
    Affected if The installed version of navigation2 is within the affected range and nav2_planner component is loaded
  2. Confirm nav2_planner component is in use
    Check your ROS2 launch files or composable node configurations for references to 'nav2_planner/PlannerServer' or 'nav2_planner' component. Also check running processes with 'ps aux | grep -i planner'
    Affected if The nav2_planner component is actively running or configured in the ROS2 system
  3. Inspect YAML configuration files loaded by nav2_planner
    Review the YAML configuration files specified in your nav2_planner launch configurations. Look for 'planner_server' or 'nav2_planner' param files specified via 'params_file' or 'yaml' arguments in launch files
    Affected if Custom or untrusted YAML configuration files are being loaded by nav2_planner, as this is the attack vector for the buffer overflow
  4. Check file permissions on YAML configs
    Examine file permissions on YAML config files used by nav2_planner using 'ls -la <config_file.yaml>' to determine if non-privileged users can modify these files
    Affected if YAML configuration files loaded by nav2_planner are writable by non-privileged users, allowing potential injection of malicious content
  5. Verify YAML parsing implementation
    Review the nav2_planner source code or configuration to identify which YAML parser is in use. Check if the package uses a safe parsing library by inspecting CMakeLists.txt or package dependencies
    Affected if The nav2_planner implementation lacks bounds checking on YAML-parsed content before buffer operations

A system is affected if it runs nav2_planner from ROS2 Humble with an affected navigation2 version and loads YAML configuration files, particularly if those files have permissive write access.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict input validation and bounds checking on YAML configuration file parsing in nav2_planner, specifically validating buffer lengths before copying data from parsed YAML content. Consider using safe YAML parsing libraries that prevent buffer overflows.

Recommended fix Moderate confidence

ros-humble-navigation2 (latest patched version in Humble distribution)

  1. 1. Identify the current version of navigation2 packages installed: `ros2 pkg list | grep navigation2`
  2. 2. Check for available updates: `sudo apt update && apt list --upgradable | grep navigation2`
  3. 3. Upgrade the navigation2 packages to the latest available version in the ROS2 Humble distribution: `sudo apt upgrade` or specifically `sudo apt install ros-humble-navigation2`
  4. 4. Rebuild any custom workspaces that depend on navigation2 after the upgrade: `colcon build --packages-up-to <your_packages>`
  5. 5. Verify the fix by checking the updated version matches the patched release
Caveat Custom planner plugins or configuration files may require testing against the updated navigation2 API if using non-standard plugins

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37862 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-37862 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data