OzoneApplication · Apache
CVE-2021-36372
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn Apache Ozone versions prior to 1.2.0, block tokens (access credentials) are persistently stored in the metadata database rather than being generated transiently. Authenticated users with key permission can retrieve these stored tokens, and critically, they can continue using these tokens even after their access has been revoked—a classic authorization bypass where persisted credentials are not invalidated upon permission revocation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
OzoneApplication
< 1.2.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Apache Ozone versionRun 'ozone version' or check the RPM/package version installed on your system. Alternatively, check the Ozone manager UI or API for the version endpoint.Affected if The version is prior to 1.2.0 (for example, 1.1.0, 1.0.x, or older releases).
-
Locate the Ozone metadata databaseIdentify the database configured for Ozone (typically RocksDB-based). Check the ozone-site.xml configuration for 'ozone.metadata.dirs' or similar metadata directory settings.Affected if A metadata database directory exists and contains Ozone's persistent storage.
-
Verify token handling behaviorReview audit logs or access records for block token usage. Check if tokens appear in the metadata database or if the system relies on on-demand token generation rather than retrieval from storage.Affected if Block tokens are being retrieved from the metadata database rather than generated transiently for each access request.
-
Test token revocation effectivenessGrant a user key permission, obtain a block token, then revoke the permission. Attempt to use the previously obtained token.Affected if The token remains valid and grants access after permission has been revoked, indicating persisted tokens are not invalidated.
You are affected if running Apache Ozone version 1.2.0 or earlier AND block tokens are stored persistently in the metadata database rather than generated transiently per request.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.2.0
Upgrade Apache Ozone to version 1.2.0 or later to ensure block tokens are not persisted to the database and access revocation is properly enforced.
1.2.0
- Identify current Apache Ozone version using 'ozone version' or checking the deployed artifacts
- Stop all Ozone services ( Ozone Manager, Storage Container Manager, DataNodes)
- Backup current Ozone configuration and metadata database
- Upgrade Ozone packages to version 1.2.0 or later using your package manager or by downloading from https://ozone.apache.org/downloads/
- Verify integrity of configuration files post-upgrade
- Restart Ozone services in the correct order: first DataNodes, then Storage Container Manager, then Ozone Manager
- Verify cluster health using 'ozone admin cluster -health'
- Test block token generation and access revocation to confirm the fix is effective
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ozone
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-36372 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-36372 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data