CVE-2021-36372 Original block tokens are persisted and can be retrieved
Authenticated users can retain access to data via persisted block tokens even after permissions are revoked in Apache Ozone.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2021-36372?
CVE-2021-36372 is a critical vulnerability in Apache Ozone, published on 19 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
In Apache Ozone versions prior to 1.2.0, Initially generated block tokens are persisted to the metadata database and can be retrieved with authenticated users with permission to the key. Authenticated users may use them even after access is revoked.
Weakness: CWE-273
Which versions are affected by CVE-2021-36372?
2 open source packages ship an affected version, including org.apache.ozone:ozone-main. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.apache.ozone:ozone-main Maven | All versions | 1.2.0 |
org.apache.ozone:ozone-main Maven | All versions | 1.2.0 |
Products include Apache Ozone.
How do I fix CVE-2021-36372?
Upgrade org.apache.ozone:ozone-main to 1.2.0 or later.
Is CVE-2021-36372 being exploited?
There is no known exploitation of CVE-2021-36372 in the wild and no public exploit code.
Other vulnerabilities in Apache Ozone
- CVE-2021-39231 Missing authentication/authorization on internal RPC endpoints
- CVE-2021-39233 Container-related datanode operations can be called without authorization
- CVE-2021-39232 Missing admin check for SCM related admin commands
- CVE-2021-39236 Owners of the S3 tokens are not validated
- CVE-2024-45106 Apache Ozone: Improper authentication when generating S3 secrets
Sources
Also known as GHSA-86fh-j58m-7pf5.