dbcve.org
NomadApplication · Hashicorp

CVE-2022-24685

HIGH · 7.5 CVSS v3.1 Published 2022-02-28
Fix available
A fix is available. Upgrade to 1.1.12 / 1.2.6 or later.
See remediation →
84/100
Remediation priority · High
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 1.0.17, 1.1.11, and 1.2.5 allow invalid HCL for the jobs parse endpoint, which may cause excessive CPU usage. 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

The jobs parse endpoint in HashiCorp Nomad versions 1.0.17, 1.1.11, and 1.2.5 does not properly validate HCL (HashiCorp Configuration Language) input. When invalid HCL is submitted to this endpoint, the parser enters a computational loop causing excessive CPU consumption, resulting in denial of service.

MitigationUpgrade Nomad to version 1.0.18, 1.1.12, or 1.2.6 (or later). As a temporary mitigation, implement rate limiting or API gateway restrictions on the jobs parse endpoint to limit malformed request volume.

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.0, <= 1.0.17>= 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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 version
    Run `nomad version` or check the Nomad binary that is running. Alternatively, query the `/v1/agent/self` API endpoint to retrieve the version information.
    Affected if The installed version falls within these ranges: 1.0.0 to 1.0.17, 1.1.0 to 1.1.11, or 1.2.0 to 1.2.5.
  2. Verify API port exposure
    Check if the Nomad API port (default 4646) is listening and accessible from network locations that could send malicious requests. Review firewall rules and network ACLs.
    Affected if The Nomad API port is open to untrusted networks or the internet without protective filtering.
  3. Confirm API authentication status
    Review Nomad configuration for `api` stanza and verify whether ACLs are enabled and enforce authentication on the `/v1/jobs/parse` endpoint.
    Affected if The jobs parse endpoint is accessible without authentication or ACL enforcement.
  4. Assess rate limiting or gateway protection
    Inspect any API gateway, load balancer, or reverse proxy in front of Nomad to determine if request rate limiting or input validation is configured for the jobs parse endpoint.
    Affected if No rate limiting or input validation is applied to the jobs parse endpoint.

You are affected if your Nomad version is 1.0.0-1.0.17, 1.1.0-1.1.11, or 1.2.0-1.2.5 AND the jobs parse endpoint is accessible without sufficient rate limiting or authentication controls.

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.1.12 / 1.2.6 or later
Fixed in 1.1.121.2.6
Interim mitigation

Upgrade Nomad to version 1.0.18, 1.1.12, or 1.2.6 (or later). As a temporary mitigation, implement rate limiting or API gateway restrictions on the jobs parse endpoint to limit malformed request volume.

Recommended fix High confidence

Nomad 1.0.18, 1.1.12, or 1.2.6 (depending on your current minor version branch)

  1. 1. Identify your current Nomad version using `nomad version`
  2. 2. Select the appropriate fixed version based on your current branch: 1.0.x users go to 1.0.18, 1.1.x users go to 1.1.12, 1.2.x users go to 1.2.6
  3. 3. Download the corresponding Nomad binary from https://www.nomadproject.io/downloads
  4. 4. Stop the Nomad service on all cluster nodes (leader first, then followers)
  5. 5. Replace the Nomad binary at the installation path (e.g., `/usr/bin/nomad` or your custom path)
  6. 6. Verify the new version with `nomad version`
  7. 7. Start the Nomad service, starting with the leader node
  8. 8. Verify cluster health using `nomad server members` and `nomad status`
Caveat Review the release notes for your target version to check for any breaking changes between your current and target version

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

Fix this in Nomad Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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