CVE-2021-36372: Improper Privilege Management in Apache Ozone

org.apache.ozone:ozone-main Updated 02 Oct 2025

Summary

23/11/2021
Yes i
Critical
9.8

CVE-2021-36372: Improper Privilege Management in Apache Ozone. Affects org.apache.ozone:ozone-main versions < 1.2.0. Fixed in 1.2.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

Apache Ozone is an open-source object store designed for high-performance, scalable, and reliable storage of large datasets. It provides a distributed file system that allows users to store and retrieve data using a key-value interface. The 'org.apache.ozone:ozone-main' package is a core component of Apache Ozone, responsible for managing block tokens and access permissions. This vulnerability affects versions prior to 1.2.0 of Apache Ozone.

Vulnerability Detail

The vulnerability in Apache Ozone (CVE-2021-36372) is related to improper privilege management. Initially generated block tokens, which are used for access control, are stored in the metadata database. Authenticated users with permission to the key can retrieve these tokens and continue to use them even after their access has been revoked. This can lead to unauthorized access and potential data breaches.

How To Fix

Minimum fixed version

1.2.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version of Apache Ozone to address the issue.

Conclusion

The vulnerability in Apache Ozone (CVE-2021-36372) allows authenticated users to continue using initially generated block tokens even after their access has been revoked. To mitigate this risk, it is crucial to upgrade to Apache Ozone version 1.2.0 or later. This upgrade ensures that the tokens are properly invalidated and prevents unauthorized access. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.apache.ozone:ozone-main →

Share this vulnerability

FAQ

Apache Ozone is an open-source object store designed for high-performance, scalable, and reliable storage of large datasets. It provides a distributed file system that allows users to store and retrieve data using a key-value interface.

This vulnerability allows authenticated users with permission to the key to continue using initially generated block tokens even after their access has been revoked. This can lead to unauthorized access and potential data breaches.

To fix this vulnerability, it is recommended to upgrade to Apache Ozone version 1.2.0 or later. This upgrade ensures that initially generated block tokens are properly invalidated and cannot be used by authenticated users after their access is revoked.

There is no known workaround for this vulnerability. It is essential to upgrade to the fixed version of Apache Ozone to address the issue.

You can find more information about Apache Ozone on the official Apache Ozone website or the project's GitHub repository.

Related vulnerabilities

Recent vulnerabilities recorded for org.apache.ozone:ozone-main.

How To Fix

Minimum fixed version

1.2.0

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback