dbcve.org
OzoneApplication · Apache

CVE-2021-39231

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, Various internal server-to-server RPC endpoints are available for connections, making it possible for an attacker to download raw data from Datanode and Ozone manager and modify Ratis replication configuration.

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 versions prior to 1.2.0, internal server-to-server RPC endpoints lack proper authentication/authorization controls, allowing unauthenticated attackers to access these internal interfaces. This enables both data exfiltration from Datanodes and Ozone Manager, as well as modification of Ratis replication configuration, potentially leading to data theft or manipulation of data redundancy.

MitigationUpgrade Apache Ozone to version 1.2.0 or later. If immediate upgrade is not possible, restrict network access to internal RPC ports using firewall rules or network segmentation to prevent external access.

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. Determine installed Apache Ozone version
    Run 'ozone version' or check the ozone-common or ozone-hdfs-*.jar file version in /usr/local/ozone/lib/ or /opt/ozone/lib/, or query the Ozone Manager REST API at /jmx?qry=Hadoop:service=OzoneManager,name=OzoneManagerInfo
    Affected if The version is below 1.2.0 (for example, 1.1.0, 1.1.1, 1.0.0, etc.)
  2. Identify exposed RPC service ports
    Check configuration files (ozone-site.xml) for properties ozone.datanode.id, hdds.datanode.port, and look for ports 9864 (Datanode), 9866 (Datanode RPC), 9867 (Datanode HTTPS), 9888 (OzoneManager), 9872 (StorageContainerManager). Use 'netstat -tlnp' or 'ss -tlnp' to list listening ports.
    Affected if Any of these internal RPC ports are bound to 0.0.0.0 or an external IP rather than 127.0.0.1 or an internal-only network interface
  3. Verify RPC authentication configuration
    In ozone-site.xml, inspect properties: hdds.datanode.authentication.method, hdds.datanode.kerberos.principal, ozone.security.enabled, and ozone.security.kerberos.enabled. Also check if 'hadoop.security.authentication' is set to 'simple' instead of 'kerberos'.
    Affected if Authentication is disabled (value is 'simple' or property is missing/false) on Datanode or OzoneManager RPC services
  4. Check Ratis replication configuration accessibility
    Inspect ozone-site.xml for 'hdds.ratis.enabled' and verify whether the Ratis RPC port (usually 9858 or 9862) is exposed externally via netstat/ss. Also check if 'hdds.ratis.snapshot.enabled' is configured without authentication.
    Affected if Ratis is enabled and its RPC port is bound to a publicly accessible interface (0.0.0.0)
  5. Confirm network accessibility of internal interfaces
    From an external or untrusted host, attempt to reach the Datanode RPC port (9866) and OzoneManager port (9888) using 'telnet <target> 9866' or 'nc -zv <target> 9888'. Alternatively, review firewall rules using 'iptables -L' or 'firewall-cmd --list-all'.
    Affected if Internal RPC ports are reachable from untrusted networks or the firewall permits unrestricted access to these ports

You are affected if Apache Ozone version is below 1.2.0 AND internal RPC ports are accessible from untrusted networks, or if RPC authentication is disabled or misconfigured in ozone-site.xml.

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. If immediate upgrade is not possible, restrict network access to internal RPC ports using firewall rules or network segmentation to prevent external access.

Recommended fix High confidence

1.2.0

  1. 1. Inventory current Apache Ozone deployment and confirm the exact version number is below 1.2.0
  2. 2. Review Apache Ozone 1.2.0 release notes and upgrade documentation for any migration requirements
  3. 3. Create a backup of all Ozone configuration files (ozone-site.xml, core-site.xml, and any custom configs)
  4. 4. If running in a cluster, plan for a rolling upgrade following Apache Ozone upgrade procedures
  5. 5. Stop Ozone services (Ozone Manager, Datanode, Storage Container Manager) in the correct order
  6. 6. Upgrade Apache Ozone to version 1.2.0 or later
  7. 7. Restore configuration files to the upgraded installation
  8. 8. Start Ozone services in the correct order (Datanodes first, then Storage Container Manager, then Ozone Manager)
Caveat Review 1.2.0 release notes for any configuration or feature changes; major version upgrades may require migration steps

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

Fix this in Ozone Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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