Authenticated cross-namespace privilege escalation via default ACLs
Published Dec 12, 2021 · Updated Aug 4, 2024
Incorrect authorization in HashiCorp Consul Enterprise allows remote authenticated users to gain permissions across namespaces through an ACL token. Namespace creation and editing accepted default ACL policies or roles without requiring acl:write permission in the default namespace. Exploitation requires an ACL token with default operator:write permission in one namespace and grants any permissions across all namespaces.
Summary
What happened
Incorrect authorization in HashiCorp Consul Enterprise allows remote authenticated users to gain permissions across namespaces through an ACL token. Namespace creation and editing accepted default ACL policies or roles without requiring acl:write permission in the default namespace. Exploitation requires an ACL token with default operator:write permission in one namespace and grants any permissions across all namespaces.
The record
- CVE
- CVE-2021-41805
- Published
- Dec 12, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-863, T1068
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 12, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo