dbcve.org
OzoneApplication · Apache

CVE-2021-39235

MEDIUM · 6.5 CVSS v3.1 Published 2021-11-19
Fix available
A fix is available. Upgrade to 1.2.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
In Apache Ozone before 1.2.0, Ozone Datanode doesn't check the access mode parameter of the block token. Authenticated users with valid READ block token can do any write operation on the same block.

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 confidence

In Apache Ozone before 1.2.0, the Datanode does not validate the access mode parameter of block tokens. This allows authenticated users possessing only a valid READ block token to perform WRITE operations on the same block, bypassing the intended authorization enforcement.

MitigationUpgrade Apache Ozone to version 1.2.0 or later which implements proper block token access mode validation at the Datanode.

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
Affected:< 1.2.0

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Apache Ozone version
    Run 'ozone version' or check the package manager for the installed ozone package version
    Affected if The installed version is any version prior to 1.2.0 (e.g., 1.0.0, 1.1.0, 1.1.1)
  2. Verify block token security is enabled
    Check the Ozone configuration file (ozone-site.xml) for property 'ozone.security.enable' set to 'true', or check if 'hdds.security.enabled' is set to true
    Affected if Block token security is enabled (the vulnerability only applies when block tokens are in use)
  3. Check if Ozone manager and Datanode components are running vulnerable versions
    Query the Ozone manager and Datanode REST APIs or logs for version information: 'ozone admin info' or check process start-up logs for version strings
    Affected if Either the Ozone manager or Datanode component reports a version below 1.2.0 while block token security is active

You are affected if Apache Ozone is installed at a version below 1.2.0 AND block token security (ozone.security.enable or hdds.security.enabled) is configured as true.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.2.0 or later
Fixed in 1.2.0
Interim mitigation

Upgrade Apache Ozone to version 1.2.0 or later which implements proper block token access mode validation at the Datanode.

Recommended fix High confidence

Apache Ozone 1.2.0 or later

  1. 1. Identify the current Apache Ozone version by running 'ozone version' or checking the deployed packages.
  2. 2. Download Apache Ozone version 1.2.0 or later from the official Apache Ozone releases (https://ozone.apache.org/downloads/).
  3. 3. Stop the Ozone cluster services (Ozone Manager, Storage Container Manager, Datanode).
  4. 4. Backup the Ozone metadata and configuration directories before upgrading.
  5. 5. Install the new Ozone 1.2.0+ packages using the appropriate package manager or manual installation method for your deployment.
  6. 6. Review and update configuration files if needed to match any new default settings in version 1.2.0+.
  7. 7. Start the Ozone cluster services in the correct order (Datanodes first, then Storage Container Manager, then Ozone Manager).
  8. 8. Verify the upgrade by checking that block tokens now properly validate access modes - users with READ tokens should no longer be able to perform WRITE operations.
Caveat Review release notes for 1.2.0 for any configuration or API changes that may affect existing integrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ozone Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-39235 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-39235 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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