# CVE-2024-10005: Consul L7 Intentions Vulnerable To URL Path Bypass

> Attackers can bypass HTTP path-based access rules in Consul L7 intentions by manipulating URL paths, requiring specific configuration to exploit.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Oct 2024
- **Updated:** 10 Jan 2025
- **Also known as:** BIT-consul-2024-10005, CLEANSTART-2026-AW78522, DEBIAN-CVE-2024-10005, GHSA-chgm-7r52-whjj, GO-2024-3243, UBUNTU-CVE-2024-10005

## What is CVE-2024-10005?

CVE-2024-10005 is a high-severity path traversal vulnerability in HashiCorp Consul, published on 30 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-10005?

4 open source packages ship an affected version, including github.com/hashicorp/consul and consul. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/hashicorp/consul` | Go | From 1.9.0 | 1.20.1 |
| `github.com/hashicorp/consul` | Go | From 1.9.0 | 1.20.1 |
| `github.com/hashicorp/consul` | Go | From 1.9.0 | 1.20.1 |
| `consul` | Bitnami | From 1.9.0 | 1.20.1 |

Products: Hashicorp Consul.

## How do I fix CVE-2024-10005?

Upgrade github.com/hashicorp/consul to 1.20.1 or later.

## Is CVE-2024-10005 being exploited?

There is no known exploitation of CVE-2024-10005 in the wild and no public exploit code.

Public exploit code:

- Security-maintained Consul v1.16.4, the last MPL-2.0 release: ReadyStack backports (CVE-2024-10005, CVE-2024-10006). See READYSTACK.md. (github_poc): https://github.com/ReadyStackFree/consul

## Other vulnerabilities in HashiCorp Consul

- [CVE-2021-41805](https://insights.sbomify.com/CVE-2021-41805/): Privilege escalation in n/a (high 8.8)
- [CVE-2021-37219](https://insights.sbomify.com/CVE-2021-37219/): HashiCorp Consul Privilege Escalation Vulnerability (high 8.8)
- [CVE-2023-2816](https://insights.sbomify.com/CVE-2023-2816/): Consul Envoy Extension Downsteam Proxy Configuration By Upstream Service Owner (high 8.7)
- [CVE-2024-10006](https://insights.sbomify.com/CVE-2024-10006/): Consul L7 Intentions Vulnerable To Headers Bypass (high 8.3)
- [CVE-2019-8336](https://insights.sbomify.com/CVE-2019-8336/): HashiCorp Consul Access Restriction Bypass (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-10005 and fix it if it is affected.

What it is: CVE-2024-10005 is a high-severity path traversal vulnerability in HashiCorp Consul, published on 30 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-10005 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/hashicorp/consul (Go): affected from 1.9.0; fixed in 1.20.1
- github.com/hashicorp/consul (Go): affected from 1.9.0; fixed in 1.20.1
- github.com/hashicorp/consul (Go): affected from 1.9.0; fixed in 1.20.1
- consul (Bitnami): affected from 1.9.0; fixed in 1.20.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-10005/ (Markdown: https://insights.sbomify.com/CVE-2024-10005/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-10005
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-10005
- OSV: https://osv.dev/vulnerability/CVE-2024-10005

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-10005/
Summaries are generated and may contain mistakes; the official description above is the record.