CVE-2024-10005: Consul L7 Intentions Vulnerable To URL Path Bypass
Noroxi assessment
Priority: Monitor (action score 23/100)
- Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.77% (FIRST EPSS); higher than 56.1% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: HashiCorp Consul 1.20.1; HashiCorp Consul Enterprise 1.15.15, 1.18.5, 1.19.3.
- Severity is disputed: the assigning authority (CNA) scores it 8.1, NVD 5.8.
Low priority for now. Upgrade to HashiCorp Consul 1.20.1; HashiCorp Consul Enterprise 1.15.15, 1.18.5, 1.19.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Oct 30, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.7% · 56th percentile
- CWE
- CWE-22
Report tools
Action score
23
Low priority for now.
- CVSS
- 23 / 40 · 5.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 5.8
- CNA · HashiCorp
- 8.1
- 2.3 point gap
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| hashicorp | consul | cpe:2.3:a:hashicorp:consul |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (HashiCorp). Independent of NVD's CPE analysis and usually ahead of it.
HashiCorp Consul
- 1.9.0 and later · before 1.20.1affected · semver
HashiCorp Consul Enterprise
- 1.9.0 and later · before 1.20.1affected · semverfixed in 1.19.3, 1.18.5, 1.15.15
Affected versions · NVD (5)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- hashicorp consul1.4.1 and later · before 1.20.1
- hashicorp consul1.9.0 and later · before 1.15.15
- hashicorp consul1.18.0 and later · before 1.18.5
- hashicorp consul1.19.0 and later · before 1.19.3
- hashicorp consul1.20.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | consul | from 0 | — |
| Go | github.com/hashicorp/consul | from 1.9.0 · before 1.20.1 | 1.20.1 |
| openSUSE:Leap 15.5 | govulncheck-vulndb | before 0.0.20241104T154416-150000.1.12.1 | 0.0.20241104T154416-150000.1.12.1 |
| openSUSE:Tumbleweed | govulncheck-vulndb | before 0.0.20241104T154416-1.1 | 0.0.20241104T154416-1.1 |
| SUSE:Linux Enterprise Module for Package Hub 15 SP5 | govulncheck-vulndb | before 0.0.20241104T154416-150000.1.12.1 | 0.0.20241104T154416-150000.1.12.1 |
| SUSE:Package Hub 12 | govulncheck-vulndb | before 0.0.20241104T154416-5.1 | 0.0.20241104T154416-5.1 |
Same product
hashicorp: all recordsOther highest-scoring records for the same primary product.
- CVE-2021-41805HashiCorp Consul Enterprise before 1.8.17, 1.9.x before 1.9.11, and 1.10.x before 1.10.4 has Incorrect Access Control.45Plan
- CVE-2026-105608Consul vulnerable to an authorization bypass in service mesh registration35Monitor
- CVE-2021-37219HashiCorp Consul and Consul Enterprise 1.10.1 Raft RPC layer allows non-server agents with a valid certificate signed by the same CA to…35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-2816Jun 2, 2023 · Consul Envoy Extension Downsteam Proxy Configuration By Upstream Service Owner26Monitor
- ← EarlierCVE-2023-3518Aug 9, 2023 · JWT Auth in L7 Intentions Allow For Mismatched Service Identity and JWT Providers for Access29Monitor
- Later →CVE-2024-10006Oct 30, 2024 · Consul L7 Intentions Vulnerable To Headers Bypass23Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| HashiCorp Consul | 1.20.1 | Vendor (CNA) |
| HashiCorp Consul Enterprise | 1.15.15 | Vendor (CNA) |
| HashiCorp Consul Enterprise | 1.18.5 | Vendor (CNA) |
| HashiCorp Consul Enterprise | 1.19.3 | Vendor (CNA) |
| HashiCorp Consul Enterprise | 1.20.1 | Vendor (CNA) |
| Go:github.com/hashicorp/consul | 1.20.1 | Package registry (OSV) |
| opensuse:govulncheck-vulndb | 0.0.20241104T154416-150000.1.12.1 · openSUSE:Leap 15.5 | Package registry (OSV) |
| suse:govulncheck-vulndb | 0.0.20241104T154416-150000.1.12.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP5 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Proof-of-concept repository on GitHub | stars:0 | 2026-10-22 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- First PoC+721 d
- TodayNov 12, 2026+743 d
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
Impact can extend beyond the vulnerable component (scope changes).
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:N
nvd-primary
Root cause
A user-supplied file name is joined with the allowed directory, but the result is never checked to confirm it is still inside that directory.
The bug in code
The whole CWE-22 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
const file = path.join(ROOT, req.query.name);
res.sendFile(file);Fixed
const file = path.resolve(ROOT, req.query.name);
if (!file.startsWith(ROOT + path.sep)) {
return res.sendStatus(400);
}
res.sendFile(file);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Path TraversalCAPEC-126likelihood: High · Very High
- Using Slashes and URL Encoding Combined to Bypass Validation LogicCAPEC-64likelihood: High · High
- Manipulating Web Input to File System CallsCAPEC-76likelihood: High · Very High
- Using Escaped Slashes in Alternate EncodingCAPEC-78likelihood: High · High
- Using Slashes in Alternate EncodingCAPEC-79likelihood: High · High
ATT&CK techniques
—
Change log (2)
- Exploit maturitynone → poc
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.