CVE-2022-30324
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 version 0.2.0 up to 1.3.0 were impacted by go-getter vulnerabilities enabling privilege escalation through the artifact stanza in submitted jobs onto the client agent host. Fixed in 1.1.14, 1.2.8, and 1.3.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 confidenceThis vulnerability in HashiCorp Nomad (including Enterprise) stems from flaws in the go-getter library used by the artifact stanza for fetching job artifacts. An attacker who can submit jobs to a Nomad cluster can exploit these flaws to achieve privilege escalation and execute code on the Nomad client agent hosts, potentially taking full control of the underlying infrastructure.
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.2.0, < 1.1.14>= 1.2.0, < 1.2.8= 1.3.0CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Nomad versionRun `nomad version` on all Nomad client and server nodes to determine the exact version. For Nomad Enterprise, the version will include an 'ent' suffix.Affected if The version is >= 0.2.0 and < 1.1.14, OR >= 1.2.0 and < 1.2.8, OR = 1.3.0
-
Identify jobs using the artifact stanzaReview all job specifications submitted to the cluster. Look for the `artifact` stanza within job files, which is used to fetch external resources such as archives, files, or git repositories.Affected if Any job specification contains an artifact stanza that fetches from untrusted or user-controlled sources
-
Verify job submission permissionsCheck the Nomad ACL policy associated with users or groups who can submit jobs. Run `nomad acl policy list` and review the capabilities of policies attached to operator accounts.Affected if Users other than trusted administrators have permissions to submit or modify jobs (submit-job capability)
If the Nomad version falls within the affected ranges AND any job uses the artifact stanza to fetch artifacts from external sources, the environment is vulnerable to remote code execution via artifact fetching.
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.1.141.2.8
Upgrade Nomad to version 1.1.14, 1.2.8, or 1.3.1 (or later stable releases) to remediate the go-getter vulnerabilities. If immediate patching is not possible, restrict job submission permissions to trusted users only.
1.1.14, 1.2.8, or 1.3.1 (or latest stable in respective minor version line)
- Identify current Nomad version using `nomad version` command
- For Nomad 1.1.x deployments: upgrade to version 1.1.14 or later (recommended: 1.1.x latest stable)
- For Nomad 1.2.x deployments: upgrade to version 1.2.8 or later (recommended: 1.2.x latest stable)
- For Nomad 1.3.0 deployments: upgrade to version 1.3.1 or later (recommended: 1.3.x latest stable)
- Plan upgrade following HashiCorp Nomad upgrade guides - typically requires rolling restart of client agents
- After upgrade, verify the artifact stanza functionality works as expected and the vulnerability is mitigated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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 $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-30324 — 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-30324 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