Privilege escalation via API key privilege assignment
Published Mar 31, 2020 · Updated Aug 4, 2024
Elasticsearch 6.7.0 through 6.8.7 and 7.0.0 through 7.6.1 allows remote authenticated users who can create API keys to gain elevated privileges. The API-key security flow accepts a newly generated key through a sequence that assigns privileges exceeding the creator's authorization. Exploitation requires API-key creation rights; successful abuse lets the attacker use the elevated key for unauthorized data access, modification, or service disruption.
Summary
What happened
Elasticsearch 6.7.0 through 6.8.7 and 7.0.0 through 7.6.1 allows remote authenticated users who can create API keys to gain elevated privileges. The API-key security flow accepts a newly generated key through a sequence that assigns privileges exceeding the creator's authorization. Exploitation requires API-key creation rights; successful abuse lets the attacker use the elevated key for unauthorized data access, modification, or service disruption.
The record
- CVE
- CVE-2020-7009
- Published
- Mar 31, 2020
- Updated
- Aug 4, 2024
- Vendor
- Elastic
- Product
- Elasticsearch
- Classifications
- CWE-266, CWE-269, T1098
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 31, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=All versions from 6.7.0 before 6.8.8 and 7.0.0 before 7.6.2
What conditions does exploitation require?
What is affected?
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