# CVE-2021-41805: Privilege escalation in n/a

> Attackers with an ACL token in one namespace can escalate privileges in another namespace due to incorrect access control in HashiCorp Consul Enterprise.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 12 Dec 2021
- **Updated:** 4 Aug 2024
- **Also known as:** BIT-consul-2021-41805, GHSA-crxx-35wq-w63c, UBUNTU-CVE-2021-41805

## What is CVE-2021-41805?

CVE-2021-41805 is a high-severity vulnerability in n/a, published on 12 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

HashiCorp 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. An ACL token (with the default operator:write permissions) in one namespace can be used for unintended privilege escalation in a different namespace.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2021-41805?

1 open source package ship an affected version, including consul. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `consul` | Bitnami | From 1.7.0 | 1.8.17, 1.9.11, 1.10.4 |

Products: Hashicorp Consul.

## How do I fix CVE-2021-41805?

Upgrade consul to a fixed version for your release line: 1.8.17, 1.9.11 or 1.10.4.

## Is CVE-2021-41805 being exploited?

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

Public exploit code:

- HashiCorp Consul exploit with python. (CVE-2021-41805) (github_poc): https://github.com/blackm4c/CVE-2021-41805
- A proof-of-concept for CVE-2021-41805 which is a vulnerability in HashiCorp Consul Enterprise allowing for Remote Code Execution (RCE) with escalated privileges. (github_poc): https://github.com/acfirthh/CVE-2021-41805

## Other vulnerabilities in n/a

- [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-2024-10005](https://insights.sbomify.com/CVE-2024-10005/): Consul L7 Intentions Vulnerable To URL Path Bypass (high 8.1)
- [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-2021-41805 and fix it if it is affected.

What it is: CVE-2021-41805 is a high-severity vulnerability in n/a, published on 12 Dec 2021. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41805 in the wild and no public exploit code.

Affected packages and fixed versions:
- consul (Bitnami): affected from 1.7.0; fixed in 1.8.17, 1.9.11, 1.10.4

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-2021-41805/ (Markdown: https://insights.sbomify.com/CVE-2021-41805/index.md)
```

## Sources

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

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