Post-revocation block-token access via persisted tokens
Published Nov 19, 2021 · Updated Aug 4, 2024
Improper privilege handling in Apache Ozone before 1.2.0 allows remote authenticated users to reuse revoked block tokens via key access requests. Ozone persists initially generated block tokens in its metadata database and returns them to users authorized for the key, without invalidating those tokens when access is revoked. The impact is continued access to protected blocks after revocation; exploitation requires valid authentication and permission to the affected key.
Summary
What happened
Improper privilege handling in Apache Ozone before 1.2.0 allows remote authenticated users to reuse revoked block tokens via key access requests. Ozone persists initially generated block tokens in its metadata database and returns them to users authorized for the key, without invalidating those tokens when access is revoked. The impact is continued access to protected blocks after revocation; exploitation requires valid authentication and permission to the affected key.
The record
- CVE
- CVE-2021-36372
- Published
- Nov 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Ozone
- Classifications
- CWE-273, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 19, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.1 <=1.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.
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