Sensitive header disclosure via async search storage
Published Jan 14, 2021 · Updated Aug 3, 2024
Information disclosure in Elastic Elasticsearch 7.7.0 through 7.10.1 allows remote authenticated users to read other users' request headers. The async search API persists the submitting user's HTTP headers in task data where another authorized index reader can retrieve them. Exploitation requires read access to the .tasks index and another user's async-search submission, exposing credentials present in retained headers.
Summary
What happened
Information disclosure in Elastic Elasticsearch 7.7.0 through 7.10.1 allows remote authenticated users to read other users' request headers. The async search API persists the submitting user's HTTP headers in task data where another authorized index reader can retrieve them. Exploitation requires read access to the .tasks index and another user's async-search submission, exposing credentials present in retained headers.
The record
- CVE
- CVE-2021-22132
- Published
- Jan 14, 2021
- Updated
- Aug 3, 2024
- Vendor
- Elastic
- Product
- Elasticsearch
- Classifications
- CWE-522, T1552
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 14, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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=7.7.0 to 7.10.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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.
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