dbcve.org
ConsulApplication · Hashicorp

CVE-2024-10005

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 URL paths in L7 traffic intentions could bypass HTTP request path-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

In Consul and Consul Enterprise, L7 traffic intentions that use URL paths can bypass HTTP request path-based access rules, allowing unauthorized access to resources that should be restricted by path-based controls.

MitigationReview all L7 traffic intentions with path-based rules and ensure they properly enforce access controls; verify that path matching cannot be circumvented through URL manipulation.

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 Consul version
    Run `consul version` or inspect the Consul binary/version file, or query the `/v1/agent/self` API endpoint to retrieve the running version
    Affected if The installed version falls within any of the affected 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. Identify L7 traffic intentions
    Query the Consul intention API with `consul intention list -detailed` or GET `/v1/agent/intentions` to list all configured traffic intentions
    Affected if Any L7 traffic intentions exist in the Consul configuration
  3. Check for path-based intention rules
    Examine each L7 intention configuration using `consul intention get <name>` or GET `/v1/intention/<uuid>` and inspect the `Action`, `HTTPservers`, and `PathPrefix` or `PathExact` fields
    Affected if Any L7 intention specifies an HTTP path prefix or exact path match (PathPrefix, PathExact, or similar path-based criteria)
  4. Verify intention source and destination services
    Review the L7 intentions to identify which source services can reach which destination services via HTTP paths, particularly intentions allowing traffic to sensitive services
    Affected if L7 path-based intentions reference sensitive backend services or APIs that should be protected by path-level access controls

You are affected if your Consul version is within the affected ranges AND you have L7 traffic intentions configured with HTTP path-based rules that could be bypassed through URL manipulation.

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

Review all L7 traffic intentions with path-based rules and ensure they properly enforce access controls; verify that path matching cannot be circumvented through URL manipulation.

Recommended fix High confidence

Consul 1.20.1 (latest stable) or 1.19.3/1.18.5/1.15.15 depending on your current major version branch

  1. 1. Identify current Consul version using `consul --version`
  2. 2. Review current L7 traffic intention configurations to understand what path-based access rules are in place
  3. 3. Plan upgrade path based on current version - target the latest stable release in your current major version line
  4. 4. Backup Consul data and configuration files before upgrading
  5. 5. Test upgrade in non-production environment first
  6. 6. Upgrade Consul to one of the fixed versions: 1.20.1, 1.19.3, 1.18.5, or 1.15.15
  7. 7. Verify L7 traffic intentions are working correctly after upgrade
  8. 8. Confirm path-based access rules are properly enforced
Caveat Review Consul upgrade notes for your version jump; major version upgrades may have breaking changes

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-10005 — 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-10005 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