Cross-user impersonation via unchecked S3 token owner
Published Nov 19, 2021 · Updated Aug 4, 2024
Missing authorization in Apache Ozone before 1.2.0 allows remote authenticated users with valid S3 credentials to impersonate another user. OzoneDelegationTokenSecretManager accepts an S3AUTHINFO token owner without checking that it matches the signed AWS access ID. Any valid Ozone S3 credential can therefore submit a crafted Ozone Manager request under a more privileged identity and perform that identity's authorized operations.
Summary
What happened
Missing authorization in Apache Ozone before 1.2.0 allows remote authenticated users with valid S3 credentials to impersonate another user. OzoneDelegationTokenSecretManager accepts an S3AUTHINFO token owner without checking that it matches the signed AWS access ID. Any valid Ozone S3 credential can therefore submit a crafted Ozone Manager request under a more privileged identity and perform that identity's authorized operations.
The record
- CVE
- CVE-2021-39236
- Published
- Nov 19, 2021
- Updated
- Aug 4, 2024
- Vendor
- The Apache Software Foundation
- Product
- Apache Ozone
- Classifications
- CWE-862, T1134
- 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.0 <=1.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.
Public exploit references
- Apache HDDS-4763 reproduction programproof of concept · demonstrated
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