CVE-2022-24684
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.0 through 1.0.16, 1.1.11, and 1.2.5 allow operators with job-submit capabilities to use the spread stanza to panic server agents. Fixed in 1.0.18, 1.1.12, and 1.2.6.
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 confidenceA denial of service vulnerability in HashiCorp Nomad allows authenticated operators with job-submit capabilities to submit jobs using the spread stanza that triggers a panic in Nomad server agents, causing them to crash and become unavailable.
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.0, < 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Determine the installed Nomad versionRun `nomad version` on each Nomad server agent node to obtain the exact version numberAffected if The version returned falls within any of these ranges: >= 0.9.0 and < 1.0.18, >= 1.1.0 and < 1.1.12, or >= 1.2.0 and < 1.2.6
-
Verify the server is running in a clusterRun `nomad server members` or check the logs to confirm this is a server agent (not just a client)Affected if The node is a Nomad server agent (the panic occurs in server agents)
-
Identify if job-submit capabilities are grantedReview ACL policies and token scopes using `nomad acl policy list` and inspect any policies containing `submit-job` or `submit-job` capabilityAffected if Any ACL token or policy grants job-submit capability to operators who could submit malicious job specifications
You are affected if your Nomad server version is within the vulnerable ranges AND operators with job-submit capability exist in your environment, as the exploit requires an authenticated operator with this capability to submit a job using the spread stanza.
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, 1.2.6 or later. If immediate upgrade is not possible, restrict job-submit capabilities to trusted operators only.
Upgrade to Nomad 1.0.18, 1.1.12, 1.2.6, or later (1.3.x or 1.4.x recommended for latest fixes)
- Review the Nomad upgrade documentation at https://www.nomadproject.io/docs/upgrade
- Take a backup of your Nomad data directory and configuration files
- Schedule a maintenance window for the upgrade
- Upgrade Nomad server agents first (one at a time or in rolling fashion), waiting for each to rejoin the cluster
- Upgrade Nomad client agents after servers are updated (can be done in parallel or rolling)
- Verify cluster health using `nomad server members` and `nomad node status`
- Confirm the version by running `nomad version`
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2022-24684 — 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-24684 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