dbcve.org
NomadApplication · Hashicorp

CVE-2024-7625

MEDIUM · 5.8 CVSS v3.1 Published 2024-08-15
Fix available
A fix is available. Upgrade to 1.6.14 / 1.7.11 or later.
See remediation →
64/100
Remediation priority · Elevated
Remotely reachable 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
In HashiCorp Nomad and Nomad Enterprise from 0.6.1 up to 1.6.13, 1.7.10, and 1.8.2, the archive unpacking process is vulnerable to writes outside the allocation directory during migration of allocation directories when multiple archive headers target the same file. This vulnerability, CVE-2024-7625, is fixed in Nomad 1.6.14, 1.7.11, and 1.8.3. Access or compromise of the Nomad client agent at the source allocation first is a prerequisite for leveraging this vulnerability.

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

Nomad's archive unpacking during allocation directory migration contains a path traversal vulnerability (zip slip style) where multiple archive headers targeting the same file allow writes outside the intended allocation directory. An attacker with prior compromise of a source allocation can craft malicious archives that escape the allocation directory during migration.

MitigationUpgrade Nomad to version 1.6.14, 1.7.11, or 1.8.3. Prior to patching, restrict access to allocation migration functionality and monitor for anomalous archive extraction patterns.

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:>= 0.6.1, < 1.6.14>= 1.7.0, < 1.7.11>= 1.8.0, <= 1.8.3>= 1.8.0, < 1.8.3

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

CVSS:3.1/AV:N/AC:H/PR:H/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 installed Nomad version
    Run `nomad version` on the server or agent to retrieve the version string
    Affected if The version is >= 0.6.1 and < 1.6.14, OR >= 1.7.0 and < 1.7.11, OR >= 1.8.0 and < 1.8.3
  2. Verify allocation migration is in use
    Review Nomad server configuration for `migrate` stanza in job specifications or check if jobs havehistorically been moved between nodes
    Affected if Allocation migration functionality is actively used or configured in the environment
  3. Inspect archive extraction logs
    Search Nomad logs (journalctl -u nomad or log files) for entries containing 'archive', 'unpack', 'extract', or 'allocation migration' patterns around job scheduling events
    Affected if Logs show archive extraction operations occurring during allocation directory migrations
  4. Check for unexpected file creation outside allocation directories
    Monitor or audit the Nomad data directory (default /opt/nomad/data or /var/lib/nomad) for files created outside the expected allocation subdirectories
    Affected if Files exist outside the intended allocation directory structure that correspond to archive extraction patterns
  5. Review job specifications for migration-enabled jobs
    Use `nomad job status` and inspect job specifications with `nomad job inspect <job>` for migrate stanza configurations
    Affected if Jobs are configured with migration settings that trigger allocation directory migration

The environment is affected if running a Nomad version within the vulnerable ranges AND allocation migration is actively used or has been used to move jobs between nodes.

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.6.14 / 1.7.11 / 1.8.3 or later
Fixed in 1.6.141.7.111.8.3
Interim mitigation

Upgrade Nomad to version 1.6.14, 1.7.11, or 1.8.3. Prior to patching, restrict access to allocation migration functionality and monitor for anomalous archive extraction patterns.

Recommended fix High confidence

Nomad 1.6.14, 1.7.11, or 1.8.3 (or later stable release)

  1. Identify the current Nomad version running in your environment using `nomad version`
  2. Review the compatibility matrix to ensure the target version is compatible with your infrastructure
  3. For Nomad open source: Upgrade the Nomad client agents to version 1.6.14, 1.7.11, or 1.8.3 (or later if available)
  4. For Nomad Enterprise: Upgrade to the corresponding Enterprise version matching the fixed releases
  5. Plan for a rolling upgrade to minimize service disruption
  6. After upgrading, verify the Nomad client agents are running the patched version using `nomad version`
  7. Ensure the archive unpacking functionality is working correctly by testing allocation migration if possible
Caveat Review HashiCorp upgrade guides for any configuration changes required between your current version and the target version; always test upgrades in a staging environment first

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

Fix this in Nomad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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