# CVE-2023-39196: Apache Ozone Improper Authentication vulnerability

> An attacker can access internal Storage Container Manager metadata without authentication, exposing non-sensitive system information.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Feb 2024
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-6726-2rx3-cgwh

## What is CVE-2023-39196?

CVE-2023-39196 is a medium-severity missing authorization vulnerability in Apache Ozone, published on 7 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Improper 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2023-39196?

2 open source packages ship an affected version, including org.apache.ozone:ozone-main. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.ozone:ozone-main` | Maven | From 1.2.0 | 1.4.0 |
| `org.apache.ozone:ozone-main` | Maven | From 1.2.0 | 1.4.0 |

Products: Apache Ozone.

## How do I fix CVE-2023-39196?

Upgrade org.apache.ozone:ozone-main to 1.4.0 or later.

## Is CVE-2023-39196 being exploited?

There is no known exploitation of CVE-2023-39196 in the wild and no public exploit code.

## Other vulnerabilities in Apache Ozone

- [CVE-2021-36372](https://insights.sbomify.com/CVE-2021-36372/): Original block tokens are persisted and can be retrieved (critical 9.8)
- [CVE-2021-39231](https://insights.sbomify.com/CVE-2021-39231/): Missing authentication/authorization on internal RPC endpoints (critical 9.1)
- [CVE-2021-39233](https://insights.sbomify.com/CVE-2021-39233/): Container-related datanode operations can be called without authorization (critical 9.1)
- [CVE-2021-39232](https://insights.sbomify.com/CVE-2021-39232/): Missing admin check for SCM related admin commands (high 8.8)
- [CVE-2021-39236](https://insights.sbomify.com/CVE-2021-39236/): Owners of the S3 tokens are not validated (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-39196 and fix it if it is affected.

What it is: CVE-2023-39196 is a medium-severity missing authorization vulnerability in Apache Ozone, published on 7 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-39196 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.ozone:ozone-main (Maven): affected from 1.2.0; fixed in 1.4.0
- org.apache.ozone:ozone-main (Maven): affected from 1.2.0; fixed in 1.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-39196/ (Markdown: https://insights.sbomify.com/CVE-2023-39196/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-39196
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-39196
- OSV: https://osv.dev/vulnerability/CVE-2023-39196

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-39196/
Summaries are generated and may contain mistakes; the official description above is the record.