dbcve.org
NomadApplication · Hashicorp

CVE-2023-3300

MEDIUM · 5.3 CVSS v3.1 Published 2023-07-20
Fix available
A fix is available. Upgrade to after 1.5.6 or later.
See remediation →
62/100
Remediation priority · Elevated
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 0.11.0 up to 1.5.6 and 1.4.1 HTTP search API can reveal names of available CSI plugins to unauthenticated users or users without the plugin:read policy. Fixed in 1.6.0, 1.5.7, and 1.4.1.

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 HTTP search API in versions 0.11.0 through 1.5.6 and 1.4.1 improperly discloses names of available CSI (Container Storage Interface) plugins to unauthenticated users or authenticated users lacking the plugin:read policy, allowing unauthorized enumeration of storage plugin infrastructure.

MitigationUpgrade Nomad to version 1.6.0, 1.5.7, or 1.4.1 to patch the authorization bypass in the HTTP search API. Network segmentation to restrict access to Nomad API endpoints can serve as an interim compensating control.

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.11.0, <= 1.4.1>= 1.5.0, <= 1.5.6

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Identify Nomad version
    Run `nomad version` on the Nomad server or client nodes to obtain the installed version string.
    Affected if The installed version falls within the vulnerable ranges: 0.11.0 through 1.4.1, or 1.5.0 through 1.5.6.
  2. Verify HTTP API accessibility
    Confirm that the Nomad HTTP API port (default 4646) is reachable from untrusted networks or by unauthenticated users. Check firewall rules and network ACLs allowing access to the Nomad API.
    Affected if The Nomad HTTP API is exposed to unauthenticated users or users without plugin:read policy.
  3. Test CSI plugin disclosure via search API
    Send a GET request to the Nomad search API endpoint (e.g., `/v1/search?type=all`) without authentication or with a token lacking the plugin:read capability, and examine the response for CSI plugin names.
    Affected if The API response contains CSI plugin names when queried by unauthenticated users or users without plugin:read policy.
  4. Review plugin:read policy assignments
    Query the Nomad ACL tokens and policies to identify users or tokens that lack the plugin:read capability, then verify whether those users can still enumerate CSI plugins via the search API.
    Affected if Users lacking plugin:read policy can retrieve CSI plugin names through the search API.

A system is affected if it runs a vulnerable Nomad version (0.11.0-1.4.1 or 1.5.0-1.5.6) with the HTTP API accessible to users who do not have the plugin:read policy, and those users can enumerate CSI plugin names through the search endpoint.

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 a release after 1.5.6
Interim mitigation

Upgrade Nomad to version 1.6.0, 1.5.7, or 1.4.1 to patch the authorization bypass in the HTTP search API. Network segmentation to restrict access to Nomad API endpoints can serve as an interim compensating control.

Recommended fix High confidence

1.6.0 (or 1.5.7 for minor-branch upgrade)

  1. 1. Identify the current Nomad version running in your environment using `nomad version`
  2. 2. If running version 0.11.0 through 1.4.1, upgrade to version 1.4.2 or later (1.5.7 or 1.6.0 recommended)
  3. 3. If running version 1.5.0 through 1.5.6, upgrade to version 1.5.7 or 1.6.0
  4. 4. Download the appropriate Nomad binary from https://www.nomadproject.io/downloads
  5. 5. Follow standard Nomad upgrade procedures: https://www.nomadproject.io/docs/upgrade
  6. 6. Verify the upgrade was successful by running `nomad version` and confirming the Search API now properly enforces plugin:read policy
Caveat Nomad upgrades may require review of breaking changes between versions; consult release notes for 1.5.7 and 1.6.0

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

Fix this in Nomad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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