dbcve.org
NomadApplication · Hashicorp

CVE-2024-6717

HIGH · 8.6 CVSS v3.1 Published 2024-07-23
Fix available
A fix is available. Upgrade to 1.7.10 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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
HashiCorp Nomad and Nomad Enterprise 1.6.12 up to 1.7.9, and 1.8.1 archive unpacking during migration is vulnerable to path escaping of the allocation directory. This vulnerability, CVE-2024-6717, is fixed in Nomad 1.6.13, 1.7.10, and 1.8.2.

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 · high confidence

This is a path traversal vulnerability in HashiCorp Nomad's archive unpacking functionality during migration operations. An attacker could exploit improper path validation during archive extraction to escape the intended allocation directory and write files to arbitrary locations on the host filesystem where the Nomad agent executes.

MitigationUpgrade Nomad to version 1.6.13, 1.7.10, or 1.8.2 (or later) to receive the patch that adds proper path validation during archive unpacking in migration workflows.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NomadApplication
Affected:>= 1.7.0, < 1.7.10= 1.6.12= 1.8.1

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
None

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

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. Check Nomad agent version
    Run 'nomad version' on the Nomad client or server nodes to obtain the installed version string
    Affected if The version is 1.7.0 through 1.7.9, exactly 1.6.12, or exactly 1.8.1
  2. Identify if migration operations are used
    Review Nomad job specifications or configuration for any jobs or processes that trigger migration operations, which invoke the archive unpacking functionality
    Affected if Migration operations are actively used or configured in the environment
  3. Check for archive-based job deployments
    Inspect job submissions or task configs for archives (zip, tar, tar.gz) that get extracted during job placement, as these trigger the vulnerable unpacking code path
    Affected if Jobs deploy archives that Nomad extracts as part of task setup
  4. Review allocation directory access
    Examine the Nomad data directory (default /opt/nomad/data or /var/lib/nomad) for evidence of files written outside the expected allocation subdirectories
    Affected if Files exist outside the expected allocation directories, suggesting potential path traversal has occurred

You are affected if your Nomad version is 1.6.12, 1.7.0-1.7.9, or 1.8.1 AND you use migration operations or deploy archive-based tasks that trigger the vulnerable archive extraction code path.

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
Upgrade available Upgrade to 1.7.10 or later
Fixed in 1.7.10
Interim mitigation

Upgrade Nomad to version 1.6.13, 1.7.10, or 1.8.2 (or later) to receive the patch that adds proper path validation during archive unpacking in migration workflows.

Recommended fix High confidence

Nomad 1.6.13, 1.7.10, or 1.8.2 depending on starting version

  1. 1. Identify the current Nomad version by running `nomad version` or checking the Nomad API.
  2. 2. Determine the target upgrade path based on current version: if on 1.6.12 upgrade to 1.6.13; if on 1.7.x (where x < 10) upgrade to 1.7.10; if on 1.8.1 upgrade to 1.8.2.
  3. 3. Review the HashiCorp Nomad upgrade guide at https://www.nomadproject.io/docs/upgrade for pre-upgrade considerations.
  4. 4. Create a backup of the Nomad state directory and configuration files.
  5. 5. For cluster upgrades, follow the rolling upgrade procedure: upgrade non-leader nodes first, then the leader last.
  6. 6. Download the appropriate Nomad binary from https://www.nomadproject.io/downloads/ matching your target version.
  7. 7. Replace the Nomad binary on all server and client nodes.
  8. 8. Restart the Nomad service on each node, starting with server nodes first.
Caveat Review Nomad upgrade notes for any between-version migrations; major version jumps may require additional migration steps

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

Fix this in Nomad Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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