dbcve.org
OzoneApplication · Apache

CVE-2021-41532

MEDIUM · 5.3 CVSS v3.1 Published 2021-11-19
Fix available
A fix is available. Upgrade to 1.2.0 or later.
See remediation →
62/100
Remediation priority · Elevated
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 before 1.2.0, Recon HTTP endpoints provide access to OM, SCM and Datanode metadata. Due to a bug, any unauthenticated user can access the data from these endpoints.

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

Apache Ozone versions before 1.2.0 contain an authentication bypass vulnerability in the Recon component. The Recon HTTP endpoints that provide access to metadata from OM (Object Manager), SCM (Storage Container Manager), and Datanodes can be accessed by any unauthenticated user due to a bug in the authentication logic.

MitigationUpgrade Apache Ozone to version 1.2.0 or later which contains the fix for this authentication bypass. As a temporary mitigation, restrict network access to Recon HTTP endpoints using firewall rules or network segmentation.

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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 installed
    Look for ozone binaries, services, or packages on the system. Common locations include /usr/bin/ozone, /opt/ozone, or check for ozone-related processes or services.
    Affected if Apache Ozone software is present on the system
  2. Determine the installed Apache Ozone version
    Run 'ozone version' or check the package manager for the installed ozone version. If source code is present, check the version file or git tags.
    Affected if The installed version is earlier than 1.2.0
  3. Check if the Recon component is enabled and running
    Identify whether the Recon service (Recon HTTP server) is configured and active. Check for recon-related processes, configuration files, or port bindings (typically port 9888).
    Affected if The Recon HTTP server is running and accessible on a network interface
  4. Test unauthenticated access to Recon endpoints
    Attempt to access a Recon REST API endpoint without providing credentials. For example, use curl to request http://<recon-host>:9888/api/v1/containers or similar metadata endpoints.
    Affected if The Recon endpoints return data or valid responses without requiring authentication credentials
  5. Verify authentication configuration for Recon
    Review the ozone-site.xml or security configuration for Recon authentication settings. Check if 'ozone.recon.http.auth.type' is set to a proper authentication mechanism (such as 'kerberos' or 'token').
    Affected if Authentication is disabled, set to 'none', or misconfigured for the Recon HTTP endpoints

The environment is affected if Apache Ozone version is earlier than 1.2.0 and the Recon component is exposed with unauthenticated access possible to its HTTP endpoints.

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 contains the fix for this authentication bypass. As a temporary mitigation, restrict network access to Recon HTTP endpoints using firewall rules or network segmentation.

Recommended fix High confidence

Apache Ozone 1.2.0

  1. Upgrade Apache Ozone to version 1.2.0 or later to resolve the unauthenticated information exposure vulnerability in Recon HTTP endpoints

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

Fix this in Ozone Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,980
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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