Internal metadata disclosure via missing mutual TLS
Published Feb 7, 2024 · Updated Feb 13, 2025
Improper authentication in Apache Ozone 1.2.0 through 1.3.0 allows remote attackers to download internal SCM metadata. An internal Storage Container Manager service endpoint fails to require and validate a mutual TLS client certificate before returning metadata. Network access to that internal endpoint is sufficient; the response is read-only, excludes user data and exposes no metadata reported as sensitive.
Summary
What happened
Improper authentication in Apache Ozone 1.2.0 through 1.3.0 allows remote attackers to download internal SCM metadata. An internal Storage Container Manager service endpoint fails to require and validate a mutual TLS client certificate before returning metadata. Network access to that internal endpoint is sufficient; the response is read-only, excludes user data and exposes no metadata reported as sensitive.
The record
- CVE
- CVE-2023-39196
- Published
- Feb 7, 2024
- Updated
- Feb 13, 2025
- Vendor
- The Apache Software Foundation
- Product
- Apache Ozone
- Classifications
- CWE-287, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 7, 2024CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.2.0 <=1.3.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo