dbcve.org
NomadApplication · Hashicorp

CVE-2023-1299

HIGH · 8.8 CVSS v3.1 Published 2023-03-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
HashiCorp Nomad and Nomad Enterprise 1.5.0 allow a job submitter to escalate to management-level privileges using workload identity and task API. Fixed in 1.5.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

HashiCorp Nomad and Nomad Enterprise 1.5.0 contain a privilege escalation vulnerability where authenticated job submitters can obtain management-level privileges by abusing the workload identity feature and task API.

MitigationUpgrade to Nomad version 1.5.1 or later to remediate this privilege escalation vulnerability.

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.0

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 Nomad client/agent, or query the /v1/agent/self API endpoint, or check the binary file version
    Affected if Version is exactly 1.5.0
  2. Verify workload identity feature status
    Check the Nomad agent configuration file (typically /etc/nomad.d/config.hcl) or query the /v1/agent/self API for the 'workload_identity' stanza enabled setting
    Affected if Workload identity is enabled in the Nomad configuration
  3. Confirm job submission permissions for non-admin users
    Review ACL policy files or use 'nomad acl policy list' to see which users/groups can submit jobs, or check the 'submit-job' ACL capability
    Affected if Non-administrator users have job submission permissions (submit-job ACL capability)

User is affected if running Nomad 1.5.0 with workload identity enabled and untrusted users have job submission permissions.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Nomad version 1.5.1 or later to remediate this privilege escalation vulnerability.

Recommended fix High confidence

1.5.1

  1. 1. Back up your Nomad data directory (typically /opt/nomad/data or /var/lib/nomad) and configuration files
  2. 2. Back up your Nomad client and server configuration files
  3. 3. Download Nomad version 1.5.1 from the official HashiCorp releases (https://www.nomadproject.io/downloads)
  4. 4. Stop the Nomad service on all nodes (server and client) using 'systemctl stop nomad' or 'sudo nomad stop -all'
  5. 5. Replace the existing Nomad binary with the version 1.5.1 binary on all nodes
  6. 6. Verify the binary version using 'nomad version' - should show 1.5.1
  7. 7. Start the Nomad service on all server nodes first, then client nodes
  8. 8. Verify cluster health using 'nomad server members' and 'nomad node status'
Caveat Minor version upgrade with security fix; no expected breaking changes, but test in staging first

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

Fix this in Nomad Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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