dbcve.org
Code InjectionWeakness · CWE-94

CVE-2024-37860

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 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_amcl 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_amcl process of ROS2 navigation2-humble. A local attacker can execute arbitrary code by providing a crafted .yaml configuration file to the nav2_amcl node, likely due to insufficient bounds checking during YAML parsing and configuration loading.

MitigationImplement proper input validation and bounds checking in the nav2_amcl YAML configuration parser. Sanitize all configuration values before use and ensure buffer sizes are not exceeded.

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. Identify nav2_amcl deployment
    Check if the nav2_amcl node is running or deployed in your ROS2 environment. Search for nav2_amcl in running processes, launch files, or container images.
    Affected if nav2_amcl is present in your environment
  2. Check navigation2-humble version
    Locate the installed version of the navigation2-humble package or nav2_amcl binary. Use commands like 'ros2 pkg version navigation2_humble' or check the package manifest. Compare against any available version information from the ROS2 distribution.
    Affected if the installed version is vulnerable and falls within the affected range for navigation2-humble
  3. Identify nav2_amcl configuration files
    Examine the launch files, parameter files, or configuration manifests that specify the .yaml configuration files loaded by nav2_amcl. Look for 'param_file', 'params_file', or similar arguments in launch configurations.
    Affected if custom .yaml configuration files are loaded by nav2_amcl
  4. Verify configuration file access controls
    Determine if the .yaml configuration files used by nav2_amcl can be modified by untrusted users or processes. Check file permissions and ownership of configuration files in the navigation2 setup.
    Affected if configuration files are writable by untrusted users or loaded from untrusted locations
  5. Audit YAML parsing behavior
    Review logs or runtime output from nav2_amcl to confirm YAML configuration parsing is occurring. Check if the node accepts configuration from external sources or network inputs.
    Affected if nav2_amcl parses YAML configuration from controllable sources

You are affected if nav2_amcl from navigation2-humble is running and loads .yaml configuration files that can be controlled by an attacker, enabling buffer overflow exploitation during YAML parsing.

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 proper input validation and bounds checking in the nav2_amcl YAML configuration parser. Sanitize all configuration values before use and ensure buffer sizes are not exceeded.

Recommended fix Moderate confidence

navigation2-humble latest version (upgrade to latest humble release that includes the security fix)

  1. 1. Identify the current version of the navigation2 package in your ROS2 humble environment by running: ros2 pkg list | grep navigation2
  2. 2. Check for available updates to the navigation2 package: sudo apt update && apt list --upgradable | grep navigation2
  3. 3. Upgrade the navigation2 package to the latest available version: sudo apt upgrade navigation2 or sudo apt install navigation2-humble --upgrade
  4. 4. Verify the upgrade was successful and note the new version number
  5. 5. Restart any running nav2_amcl nodes or the entire navigation stack to ensure the patched version is active
  6. 6. Test that legitimate YAML configuration files for AMCL still work correctly after the upgrade
  7. 7. Review your YAML configuration files to ensure they do not contain any crafted malicious content that could exploit the vulnerability
Caveat Minor: Ensure any custom AMCL parameters in YAML files conform to expected syntax after the patch, as stricter validation may have been added

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-37860 — 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-37860 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