dbcve.org
OzoneApplication · Apache

CVE-2021-39233

CRITICAL · 9.1 CVSS v3.1 Published 2021-11-19
Fix available
A fix is available. Upgrade to 1.2.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 versions prior to 1.2.0, Container related Datanode requests of Ozone Datanode were not properly authorized and can be called by any client.

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

Container-related Datanode requests in Apache Ozone lacked proper authorization checks, allowing any client to execute these sensitive operations without authentication. This authorization bypass affects the Datanode component specifically, exposing container management functionality to unauthorized access.

MitigationUpgrade to Apache Ozone 1.2.0 or later which implements proper authorization for container-related Datanode requests. As a compensating control, restrict network access to Datanodes from untrusted clients until the upgrade is completed.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Identify if Apache Ozone is deployed
    Check for ozone binaries, service processes, or installation directories. Common locations: /opt/ozone, /usr/local/ozone, or look for 'ozone' processes via 'ps aux | grep ozone' or 'systemctl list-units | grep ozone'
    Affected if Apache Ozone processes or installations are found on the system
  2. Determine the installed Ozone version
    Run 'ozone version' or check the RPM/DEB package version via 'rpm -qi ozone' or 'dpkg -l ozone'. Also check the JAR file version in installation directories
    Affected if The version is lower than 1.2.0 (e.g., 1.1.0, 1.0.0, or any version in the 1.x series before 1.2.0)
  3. Verify the Datanode service is running
    Check for ozone-datanode process: 'ps aux | grep datanode' or 'jps -l | grep DataNode'. Also check if ports 9864-9867 are listening via 'netstat -tlnp | grep -E "986[4-7]"'
    Affected if Datanode process is running and accepting connections
  4. Assess network exposure of Datanode endpoints
    Review firewall rules, network ACLs, or Kubernetes network policies controlling access to Datanode ports (9864-9867). Check if untrusted network segments can reach these ports
    Affected if Datanode ports are accessible from untrusted network segments or the public internet

You are affected if Apache Ozone version is below 1.2.0 and the Datanode service is running and accessible from untrusted clients.

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 to Apache Ozone 1.2.0 or later which implements proper authorization for container-related Datanode requests. As a compensating control, restrict network access to Datanodes from untrusted clients until the upgrade is completed.

Recommended fix High confidence

1.2.0

  1. 1. Identify the current Apache Ozone version in use by checking the Ozone distribution or running 'ozone version'
  2. 2. If the current version is prior to 1.2.0, plan an upgrade to version 1.2.0 or later
  3. 3. Review the Apache Ozone upgrade documentation for migration considerations
  4. 4. Create a backup of the current Ozone configuration files and any custom settings
  5. 5. Stop all Ozone services ( Ozone Manager, Storage Container Manager, Datanodes)
  6. 6. Upgrade Ozone packages to version 1.2.0 or the latest stable release
  7. 7. Verify the upgrade packages are correctly installed
  8. 8. Start Ozone services in the correct order (Datanodes first, then Storage Container Manager, then Ozone Manager)
Caveat Review release notes for any configuration or behavior changes between your current version and 1.2.0

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-39233 — 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-39233 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