Authenticated file disclosure via unvalidated .pbf path
Published Nov 22, 2023 · Updated Oct 11, 2024
Path traversal in Elastic Kibana 7.9.0 through 7.14.0 allows remote authenticated users to read internal .pbf files. The .pbf file loader accepts a user-supplied path without restricting traversal outside its intended directory; Elastic does not identify the handler. A low-privileged Kibana account and a crafted network request are required, and disclosure is limited to host files whose names end in .pbf.
Summary
What happened
Path traversal in Elastic Kibana 7.9.0 through 7.14.0 allows remote authenticated users to read internal .pbf files. The .pbf file loader accepts a user-supplied path without restricting traversal outside its intended directory; Elastic does not identify the handler. A low-privileged Kibana account and a crafted network request are required, and disclosure is limited to host files whose names end in .pbf.
The record
- CVE
- CVE-2021-22151
- Published
- Nov 22, 2023
- Updated
- Oct 11, 2024
- Vendor
- Elastic
- Product
- Kibana
- Classifications
- CWE-22, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 22, 2023CVE publishedPublication date reported by the CVE source.
- Oct 11, 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.9.0 <7.14.0
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