OzoneApplication · Apache
CVE-2023-39196
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 · uneditedImproper Authentication vulnerability in Apache Ozone. The vulnerability allows an attacker to download metadata internal to the Storage Container Manager service without proper authentication. The attacker is not allowed to do any modification within the Ozone Storage Container Manager service using this vulnerability. The accessible metadata does not contain sensitive information that can be used to exploit the system later on, and the accessible data does not make it possible to gain access to actual user data within Ozone. This issue affects Apache Ozone: 1.2.0 and subsequent releases up until 1.3.0. Users are recommended to upgrade to version 1.4.0, which fixes the issue.
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 confidenceImproper authentication in Apache Ozone's Storage Container Manager (SCM) allows unauthenticated attackers to download internal metadata. While read access to SCM metadata is possible, the vulnerability does not permit modifications to SCM or access to user data, and the exposed metadata contains no sensitive information.
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.0, <= 1.3.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Apache Ozone versionRun 'ozone version' or check the Ozone JAR/file version metadata, or query the SCM endpoint for version infoAffected if The installed version falls within 1.2.0 to 1.3.0 inclusive
-
Locate SCM service configurationCheck ozone-site.xml for 'ozone.scm.http-address' or 'ozone.scm.https-address' settings to find where SCM is boundAffected if SCM HTTP/HTTPS port is bound to an accessible network interface (0.0.0.0 or non-loopback IP)
-
Verify SCM metadata endpoint accessibilityAttempt an unauthenticated HTTP GET request to SCM endpoints such as /jmx or /prometheus metrics (common SCM metadata paths)Affected if The request returns metadata without requiring authentication (401/403 not returned)
-
Confirm SCM is runningCheck if the StorageContainerManager process is active via 'jps' or process management tools, looking for 'StorageContainerManager'Affected if SCM process is running and exposed on the network
You are affected if Apache Ozone version 1.2.0 through 1.3.0 is installed and the SCM service is network-accessible without authentication enforcement.
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 · scopedUpgrade Apache Ozone from affected versions (1.2.0 - 1.3.0) to version 1.4.0 or later, which includes proper authentication enforcement for SCM metadata endpoints.
1.4.0
- Upgrade Apache Ozone from version 1.2.0-1.3.0 to version 1.4.0
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Ozone
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-39196 — 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-2023-39196 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