dbcve.org
ConsulApplication · Hashicorp

CVE-2024-10006

MEDIUM · 5.8 CVSS v3.1 Published 2024-10-30
Fix available
A fix is available. Upgrade to 1.15.15 / 1.18.5 or later.
See remediation →
67/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
A vulnerability was identified in Consul and Consul Enterprise (“Consul”) such that using Headers in L7 traffic intentions could bypass HTTP header based access rules.

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 · moderate confidence

Consul's L7 traffic intentions feature allows fine-grained access control using HTTP headers. The vulnerability allows attackers to bypass these header-based access rules by using Headers in L7 traffic intentions in an unexpected way, potentially gaining unauthorized access to services.

MitigationUpgrade Consul and Consul Enterprise to the patched version addressing CVE-2024-10006. Review and audit existing L7 traffic intention configurations using HTTP header-based rules to ensure they are functioning as intended.

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
ConsulApplication
Affected:>= 1.4.1, < 1.20.1>= 1.9.0, < 1.15.15>= 1.18.0, < 1.18.5>= 1.19.0, < 1.19.3= 1.20.0

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
Changed
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/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. Check installed Consul version
    Run 'consul --version' or query the /v1/agent/self API endpoint to retrieve the running Consul version
    Affected if The installed version falls within any of these ranges: >= 1.4.1 and < 1.20.1; >= 1.9.0 and < 1.15.15; >= 1.18.0 and < 1.18.5; >= 1.19.0 and < 1.19.3; or equals exactly 1.20.0
  2. Verify L7 traffic intentions are configured
    Query the Consul intentions API at /v1/agent/intentions or check intention configuration files. Look for intentions with 'Action': 'allow' and 'HTTP' type definitions
    Affected if L7 traffic intentions with HTTP header-based rules exist in the configuration
  3. Confirm HTTP header rules are in use
    Inspect the intention configuration JSON for 'HTTPHeader' or 'Headers' fields within the 'HTTP' permission block. Use 'consul intention list -detailed' or API GET /v1/agent/intention
    Affected if Intentions contain HTTP header matching rules (header name and expected value pairs)
  4. Audit recent service traffic for anomalies
    Review Consul service mesh or proxy access logs for requests that may have bypassed expected header requirements. Check if services that should be blocked are receiving unexpected traffic
    Affected if Services are receiving traffic that should be denied based on configured header rules but are not being blocked

A user is affected if their Consul version is in the vulnerable range AND they have L7 traffic intentions configured with HTTP header-based access rules that could potentially be bypassed.

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.15.15 / 1.18.5 / 1.19.3 or later
Fixed in 1.15.151.18.51.19.3
Interim mitigation

Upgrade Consul and Consul Enterprise to the patched version addressing CVE-2024-10006. Review and audit existing L7 traffic intention configurations using HTTP header-based rules to ensure they are functioning as intended.

Recommended fix High confidence

Consul 1.20.1 (or latest 1.20.x stable)

  1. 1. Identify your current Consul version by running `consul --version`
  2. 2. Review the Consul upgrade documentation at https://developer.hashicorp.com/consul/docs/upgrades
  3. 3. Back up your Consul state directory (by default `/opt/consul/data` or `/consul/data`)
  4. 4. For clustered deployments, plan a rolling upgrade following the recommended upgrade order (non-voting first, then voting members)
  5. 5. Download the fixed version (1.20.1, 1.19.3, 1.18.5, or 1.15.15) from https://www.consul.io/downloads
  6. 6. Stop the Consul service on each node
  7. 7. Replace the Consul binary with the new version
  8. 8. Restart the Consul service
Caveat Review Consul 1.20 release notes for any breaking changes; rolling upgrades are supported but ensure compatibility with your existing API/CLI usage

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

Fix this in Consul Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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