Unauthorized access via stale replicated ACL rules
Published Jun 11, 2020 · Updated Aug 4, 2024
Improper access control in HashiCorp Consul 1.4.0 through 1.6.5 and 1.7.0 through 1.7.3 allows remote authenticated users to retain permissions. Legacy ACL conversion omits the token hash used to detect changes, so updated rules are not replicated from the primary to secondary data centers. Exploitation requires a multi-data-center deployment with token replication and an existing legacy ACL token; secondary data centers continue applying its stale permissions.
Summary
What happened
Improper access control in HashiCorp Consul 1.4.0 through 1.6.5 and 1.7.0 through 1.7.3 allows remote authenticated users to retain permissions. Legacy ACL conversion omits the token hash used to detect changes, so updated rules are not replicated from the primary to secondary data centers. Exploitation requires a multi-data-center deployment with token replication and an existing legacy ACL token; secondary data centers continue applying its stale permissions.
The record
- CVE
- CVE-2020-12797
- Published
- Jun 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1078
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 11, 2020CVE 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