dbcve.org
NomadApplication · Hashicorp

CVE-2022-41606

MEDIUM · 6.5 CVSS v3.1 Published 2022-10-12
Fix available
A fix is available. Upgrade to 1.2.13 / 1.3.6 or later.
See remediation →
71/100
Remediation priority · Elevated
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.0.2 up to 1.2.12, and 1.3.5 jobs submitted with an artifact stanza using invalid S3 or GCS URLs can be used to crash client agents. Fixed in 1.2.13, 1.3.6, and 1.4.0.

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

Nomad jobs submitted with an artifact stanza containing invalid S3 or GCS URLs can cause client agents to crash, resulting in denial of service. The vulnerability exists in the artifact URL handling code and affects client agents specifically.

MitigationUpgrade Nomad to version 1.2.13, 1.3.6, 1.4.0 or later to patch the vulnerability. Additionally, review job specifications to ensure artifact URLs are valid before deployment.

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.0.2, < 1.2.13>= 1.3.0, < 1.3.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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Nomad client agent installation
    Run 'nomad version' on the target host to confirm Nomad is installed and retrieve the version number
    Affected if Version is 1.0.2 through 1.2.12, or 1.3.0 through 1.3.5 (this indicates the client agent is vulnerable)
  2. Check if Nomad client agent service is running
    Run 'nomad node status' or check the process status (e.g., 'systemctl status nomad' or 'ps aux | grep nomad')
    Affected if A running Nomad client agent on a vulnerable version is present and could be exploited
  3. Identify jobs using artifact stanzas
    Run 'nomad job status' to list all jobs, then for each job run 'nomad job inspect <job_id>' and look for 'artifact' blocks in the job specification
    Affected if Any job contains an artifact stanza referencing S3 or GCS URLs - these could trigger the crash if the URLs are malformed
  4. Review Nomad client agent logs for crashes
    Check Nomad logs (e.g., 'nomad logs -job <alloc_id>' or journalctl for the nomad service) for evidence of crashes related to artifact fetching
    Affected if Recent crashes in logs related to artifact URL handling indicate the vulnerability may have been triggered

You are affected if a Nomad client agent is running a version between 1.0.2 and 1.2.12 or between 1.3.0 and 1.3.5 AND any Nomad jobs use artifact stanzas with S3 or GCS URLs, as malformed URLs in these artifacts can crash the client agent.

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.2.13 / 1.3.6 or later
Fixed in 1.2.131.3.6
Interim mitigation

Upgrade Nomad to version 1.2.13, 1.3.6, 1.4.0 or later to patch the vulnerability. Additionally, review job specifications to ensure artifact URLs are valid before deployment.

Recommended fix High confidence

Upgrade to Nomad 1.2.13, 1.3.6, or 1.4.0 (latest stable release)

  1. 1. Back up your Nomad configuration, state, and any critical data before upgrading.
  2. 2. Download the appropriate fixed version for your current major version: Nomad 1.2.13, 1.3.6, or 1.4.0 (recommended) from hashicorp.com or your package manager.
  3. 3. Upgrade your Nomad server agents first, followed by client agents, following your cluster's rolling upgrade procedure.
  4. 4. Verify that the Nomad agents start successfully and join the cluster properly.
  5. 5. Test submitting a job with an artifact stanza containing both valid and invalid S3/GCS URLs to confirm the vulnerability is fixed and client agents no longer crash.

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
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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 locally
dbcve dependency scanner

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