CVE-2022-24683
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 · uneditedHashiCorp Nomad and Nomad Enterprise 0.9.2 through 1.0.17, 1.1.11, and 1.2.5 allow operators with read-fs and alloc-exec (or job-submit) capabilities to read arbitrary files on the host filesystem as root.
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 confidenceThis is a file read vulnerability in HashiCorp Nomad where operators possessing specific capabilities (read-fs combined with alloc-exec, or read-fs combined with job-submit) can read arbitrary files on the host filesystem with root privileges. The issue stems from insufficient path validation allowing path traversal via the file system capability.
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>= 0.9.2, < 1.0.18>= 1.1.0, < 1.1.12>= 1.2.0, < 1.2.6CVSS 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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check Nomad server versionRun `nomad version` on the server or query the API endpoint `curl http://127.0.0.1:4646/v1/agent/self` to retrieve the version fieldAffected if The version is 0.9.2 through 1.0.17, 1.1.0 through 1.1.11, or 1.2.0 through 1.2.5 (meaning it falls within any of the three affected ranges)
-
Verify if ACLs are enabledCheck the Nomad configuration file (typically at /etc/nomad.d/nomad.hcl or /etc/nomad.conf) for the `acl` stanza with `enabled = true`, or query the API at /v1/operator/leader to confirm ACL statusAffected if ACLs are enabled and the system relies on them for access control (the vulnerability is exploitable through ACL policy grants)
-
Review ACL policies for read-fs capability grantsRun `nomad acl policy list` to enumerate all policies, then use `nomad acl policy read <policy-name>` on each to inspect for `capabilities = ["read-fs"]` grantsAffected if Any ACL policy grants the read-fs capability, as this is a required component for the exploit
-
Check if any policy combines read-fs with alloc-execExamine each ACL policy identified with read-fs and look for the presence of "alloc-exec" in the capabilities listAffected if A single policy grants both read-fs AND alloc-exec capabilities to any token, allowing path traversal via exec-based file reads
-
Check if any policy combines read-fs with job-submitExamine each ACL policy identified with read-fs and look for the presence of "job-submit" in the capabilities listAffected if A single policy grants both read-fs AND job-submit capabilities to any token, allowing path traversal via job submission file reads
You are affected if your Nomad version is in the vulnerable ranges AND you have ACL policies that grant read-fs capability in combination with either alloc-exec or job-submit to any operator token.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.181.1.121.2.6
Upgrade Nomad to version 1.0.18, 1.1.12, or 1.2.6 (or later) to patch this vulnerability. Additionally, review and restrict the allocation-exec and job-submit capabilities granted to operators to limit the blast radius of this issue.
Upgrade to Nomad 1.0.18, 1.1.12, 1.2.6, or later stable releases (1.3.x+)
- Identify the current Nomad version by running `nomad version`
- Determine which version branch you are currently on (0.9.x-1.0.x, 1.1.x, or 1.2.x)
- Download the appropriate fixed release for your branch: 1.0.18, 1.1.12, or 1.2.6 respectively, or a later stable release from hashicorp.com/downloads
- Review the Nomad upgrade guide at https://www.nomadproject.io/docs/upgrade
- Ensure you have a backup of your Nomad state and configuration
- Stop the Nomad service on all nodes in your cluster
- Upgrade the Nomad binary on all cluster nodes
- Start the Nomad service on all nodes, verifying cluster formation succeeds
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-24683 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-24683 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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