dbcve.org
NomadApplication · Hashicorp

CVE-2024-10975

HIGH · 7.7 CVSS v3.1 Published 2024-11-07
Fix available
A fix is available. Upgrade to 1.7.15 / 1.8.7 or later.
See remediation →
83/100
Remediation priority · High
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") volume specification is vulnerable to arbitrary cross-namespace volume creation through unauthorized Container Storage Interface (CSI) volume writes. This vulnerability, identified as CVE-2024-10975, is fixed in Nomad Community Edition 1.9.2 and Nomad Enterprise 1.9.2, 1.8.7, and 1.7.15.

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 volume specification contains an authorization bypass allowing unauthorized CSI (Container Storage Interface) volume writes across namespace boundaries. Users can create volumes in namespaces they shouldn't have access to by manipulating volume specifications.

MitigationUpgrade Nomad to fixed versions: Community Edition 1.9.2 or Enterprise 1.9.2/1.8.7/1.7.15 or later. Verify cross-namespace volume isolation after upgrade.

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.3.0, < 1.7.15>= 1.3.0, < 1.9.2>= 1.8.0, < 1.8.7>= 1.9.0, < 1.9.2

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

CVSS:3.1/AV:N/AC:L/PR:L/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 version
    Run `nomad version` or `nomad agent-self -json` to get the installed Nomad version.
    Affected if The version is >= 1.3.0 and < 1.7.15, OR >= 1.8.0 and < 1.8.7, OR >= 1.9.0 and < 1.9.2.
  2. Verify CSI volumes exist
    Run `nomad volume status` to list all CSI volumes in the cluster. Check if any volumes are present.
    Affected if CSI volumes are present and the Nomad version is in the affected range.
  3. Check namespace isolation
    Run `nomad namespace list` to list all namespaces, then inspect volume ownership: `nomad volume status -namespace <namespace>` for each namespace to see which users or ACL tokens can create volumes in namespaces they should not access.
    Affected if Users can create CSI volumes in namespaces outside their ACL policy grants.
  4. Review ACL policy for volume permissions
    Examine ACL policies with `nomad acl policy list` and inspect relevant policies with `nomad acl policy info <name>` to verify volume-related permissions include namespace restrictions.
    Affected if ACL policies allow volume creation across namespaces that should be isolated.

You are affected if your Nomad version is in the affected ranges AND you have CSI volumes configured with ACL policies that may allow cross-namespace volume creation.

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.15 / 1.8.7 / 1.9.2 or later
Fixed in 1.7.151.8.71.9.2
Interim mitigation

Upgrade Nomad to fixed versions: Community Edition 1.9.2 or Enterprise 1.9.2/1.8.7/1.7.15 or later. Verify cross-namespace volume isolation after upgrade.

Recommended fix High confidence

Nomad Community Edition 1.9.2 or Nomad Enterprise 1.9.2/1.8.7/1.7.15

  1. Identify your current Nomad version using `nomad version`
  2. For Nomad Community Edition: Upgrade to version 1.9.2
  3. For Nomad Enterprise: Upgrade to version 1.9.2, 1.8.7, or 1.7.15 depending on your current version (choose the nearest fixed version >= your current release)
  4. After upgrade, verify the version with `nomad version`
  5. Test that CSI volume operations work correctly in your environment

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

Fix this in Nomad Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
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,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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