dbcve.org
NomadApplication · Hashicorp

CVE-2022-24686

MEDIUM · 5.9 CVSS v3.1 Published 2022-02-14
Fix available
A fix is available. Upgrade to 1.0.18 / 1.1.12 or later.
See remediation →
68/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.3.0 through 1.0.17, 1.1.11, and 1.2.5 artifact download functionality has a race condition such that the Nomad client agent could download the wrong artifact into the wrong destination. 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 confidence

A race condition in Nomad's artifact download functionality allows the client agent to download artifacts into incorrect destinations, potentially causing files to be written to the wrong paths. This occurs during concurrent artifact fetches where destination path handling is not properly synchronized.

MitigationUpgrade Nomad to version 1.0.18, 1.1.12, 1.2.6, or later to address the race condition in artifact download destination handling.

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.3.0, < 1.0.18>= 1.1.0, < 1.1.12>= 1.2.0, < 1.2.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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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 the installed Nomad version
    Run `nomad version` to obtain the client and server version numbers
    Affected if The version falls within >= 0.3.0 and < 1.0.18, >= 1.1.0 and < 1.1.12, or >= 1.2.0 and < 1.2.6
  2. Locate job specifications using artifact downloads
    Run `nomad job status` to list all jobs, then inspect job specs with `nomad job spec <job-id>` or review HCL files for 'artifact' blocks
    Affected if Any job definition contains an artifact block that specifies source URLs to download
  3. Determine if multiple artifact-fetching jobs can run concurrently
    Review job specifications for artifact blocks and check the job count, update frequency, or deployment configuration to see if multiple instances can execute simultaneously
    Affected if More than one job with artifact blocks can run at the same time on the same node, creating the concurrent download condition
  4. Inspect recent artifact download activity
    Review Nomad client logs for entries related to artifact downloads, looking for messages containing 'artifact' and 'download' keywords
    Affected if Logs show concurrent artifact download operations occurring on the Nomad client

A Nomad installation is affected if it runs a version within the vulnerable ranges AND has jobs configured to download artifacts concurrently.

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 1.0.18 / 1.1.12 / 1.2.6 or later
Fixed in 1.0.181.1.121.2.6
Interim mitigation

Upgrade Nomad to version 1.0.18, 1.1.12, 1.2.6, or later to address the race condition in artifact download destination handling.

Recommended fix High confidence

Upgrade to 1.0.18 if on 0.x/1.0.x branch; 1.1.12 if on 1.1.x branch; or 1.2.6 if on 1.2.x branch. For newer branches, upgrade to the latest stable release that includes the fix.

  1. Identify the current Nomad version by running 'nomad version'
  2. Determine the appropriate upgrade path based on current version (see upgrade_path)
  3. Backup all Nomad configuration files and data directories
  4. For Nomad clusters: upgrade followers first, then leader (for standalone: simply stop, upgrade, and restart)
  5. Download the appropriate fixed version from https://www.nomadproject.io/downloads
  6. Upgrade the Nomad binary
  7. Restart the Nomad agent or service
  8. Verify the version upgrade: run 'nomad version' and confirm it shows the fixed release
Caveat Review HashiCorp's upgrade guides and release notes for any breaking changes between your current version and target version before upgrading.

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

Fix this in Nomad Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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