dbcve.org
NomadApplication · Hashicorp

CVE-2024-12678

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-20
Fix available
A fix is available. Upgrade to 1.7.16 / 1.8.8 or later.
See remediation →
71/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
Nomad Community and Nomad Enterprise ("Nomad") allocations are vulnerable to privilege escalation within a namespace through unredacted workload identity tokens. This vulnerability, identified as CVE-2024-12678, is fixed in Nomad Community Edition 1.9.4 and Nomad Enterprise 1.9.4, 1.8.8, and 1.7.16.

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 allocations are vulnerable to privilege escalation within a namespace through unredacted workload identity tokens. Workload identity tokens that should be restricted or redacted are being exposed, allowing users to potentially escalate their privileges within the namespace.

MitigationUpgrade Nomad to the fixed versions: Nomad Community Edition 1.9.4 or Nomad Enterprise 1.9.4, 1.8.8, or 1.7.16.

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.4.0, < 1.7.16>= 1.4.0, < 1.9.4>= 1.8.0, < 1.8.8>= 1.9.0, < 1.9.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 version
    Run `nomad version` to determine the installed version of the Nomad client and server.
    Affected if The installed version is 1.4.0 through 1.7.15, 1.8.0 through 1.8.7, or 1.9.0 through 1.9.3.
  2. Verify workload identity is enabled
    Examine the Nomad configuration file (typically at /etc/nomad.d/nomad.hcl or nomad.conf) for the `workload_identity` stanza or check the Nomad server API at /v1/agent/config for the workload_identity section.
    Affected if Workload identities are enabled in the Nomad configuration.
  3. Inspect namespace token exposure
    Query the Nomad API endpoint for allocations within a namespace (e.g., `nomad alloc status -json <alloc-id>` or the /v1/allocations API) and examine if workload identity tokens appear in unredacted form in the allocation metadata or logs.
    Affected if Workload identity tokens are visible in allocation details, logs, or API responses without redaction.
  4. Review audit logs for token exposure
    Check Nomad audit logs (if enabled) for entries that may contain unredacted workload identity tokens in API responses or event data.
    Affected if Audit logs show workload identity tokens being exposed in responses where they should be redacted.

You are affected if your Nomad version falls within 1.4.0-1.7.15, 1.8.0-1.8.7, or 1.9.0-1.9.3 and workload identities are enabled with tokens being exposed in allocation data or API responses.

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.16 / 1.8.8 / 1.9.4 or later
Fixed in 1.7.161.8.81.9.4
Interim mitigation

Upgrade Nomad to the fixed versions: Nomad Community Edition 1.9.4 or Nomad Enterprise 1.9.4, 1.8.8, or 1.7.16.

Recommended fix High confidence

Nomad Community Edition 1.9.4+ or Nomad Enterprise 1.9.4/1.8.8/1.7.16 (choose latest in your release branch)

  1. 1. Identify your current Nomad version by running `nomad version`
  2. 2. Determine if you are using Nomad Community Edition or Nomad Enterprise
  3. 3. For Nomad Community Edition: upgrade to version 1.9.4 or later
  4. 4. For Nomad Enterprise: upgrade to version 1.9.4, 1.8.8, or 1.7.16 depending on your release branch (choose the latest in your branch)
  5. 5. Before upgrading, back up your Nomad data directory and configuration files
  6. 6. Perform the upgrade following HashiCorp's standard upgrade procedure
  7. 7. After upgrade, verify workloads function correctly and that workload identity tokens are properly handled
Caveat Review HashiCorp upgrade guides for any between-version considerations; test in staging before production deployment

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

Fix this in Nomad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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