dbcve.org
NomadApplication · Hashicorp

CVE-2024-1329

HIGH · 7.5 CVSS v3.1 Published 2024-02-08
Fix available
A fix is available. Upgrade to 1.5.14 / 1.6.7 or later.
See remediation →
84/100
Remediation priority · High
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.5.13 up to 1.6.6, and 1.7.3 template renderer is vulnerable to arbitrary file write on the host as the Nomad client user through symlink attacks. This vulnerability, CVE-2024-1329, is fixed in Nomad 1.7.4, 1.6.7, and 1.5.14.

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

The HashiCorp Nomad template renderer contains a vulnerability (CVE-2024-1329) allowing arbitrary file write on the host as the Nomad client user through symlink attacks. This affects Nomad versions 1.5.13 through 1.6.6 and 1.7.3, enabling attackers to write files to arbitrary locations on the host filesystem by exploiting symlinks during template rendering.

MitigationUpgrade Nomad to version 1.7.4, 1.6.7, or 1.5.14 to patch the template renderer vulnerability. Additionally, review template configurations and restrict Nomad client permissions to limit the impact of potential symlink exploitation.

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.5.13, < 1.5.14>= 1.6.6, < 1.6.7>= 1.7.3., < 1.7.4

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
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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. Identify the installed Nomad version
    Run `nomad version` on the Nomad client or server nodes to retrieve the version string
    Affected if The version falls within the affected ranges: 1.5.13 to 1.5.13.x, 1.6.0 to 1.6.6, or 1.7.0 to 1.7.3
  2. Determine if Nomad client is running
    Run `nomad status` or check the agent configuration for `client` stanza enabled: inspect the Nomad configuration file (typically at /etc/nomad.d/nomad.hcl or nomad.json) for `client { enabled = true }`
    Affected if The client mode is enabled and the version is vulnerable
  3. Identify jobs using template rendering
    Run `nomad job status` to list all jobs, then inspect each job's specification with `nomad job spec <job-id>` and search for `template` stanzas that define `destination` paths
    Affected if Any job contains template stanzas with writable destination paths that could be exploited via symlinks
  4. Check template destination paths for symlink vulnerabilities
    Review the `destination` paths specified in template stanzas across all job specifications; examine if these paths or their parent directories are symlinks using `ls -la <destination-path>`
    Affected if Template destination paths point to locations that could be manipulated through symlinks or if the jobs run with permissions that allow writing outside expected directories

You are affected if you are running a vulnerable Nomad version (1.5.13 through 1.5.13.x, 1.6.0 through 1.6.6, or 1.7.0 through 1.7.3) with the client role enabled and any jobs utilizing template stanzas with writable destination paths.

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.5.14 / 1.6.7 / 1.7.4 or later
Fixed in 1.5.141.6.71.7.4
Interim mitigation

Upgrade Nomad to version 1.7.4, 1.6.7, or 1.5.14 to patch the template renderer vulnerability. Additionally, review template configurations and restrict Nomad client permissions to limit the impact of potential symlink exploitation.

Recommended fix High confidence

Nomad 1.7.4 (or 1.6.7/1.5.14 depending on your current release branch)

  1. Back up your Nomad configuration files and data directory before upgrading
  2. Stop the Nomad service on all client and server nodes
  3. Upgrade Nomad to version 1.7.4 (or 1.6.7 if remaining on the 1.6.x branch, or 1.5.14 if remaining on the 1.5.x branch) using your package manager or binary appropriate for your OS
  4. Verify the installed version matches the target fixed version (nomad --version)
  5. Restart the Nomad service
  6. Confirm Nomad is running properly and jobs execute as expected
Caveat Minimal - these are patch releases within stable branches containing security fixes only

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-1329 — 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-1329 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