dbcve.org
OzoneApplication · Apache

CVE-2024-45106

HIGH · 8.1 CVSS v3.1 Published 2024-12-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
Improper authentication of an HTTP endpoint in the S3 Gateway of Apache Ozone 1.4.0 allows any authenticated Kerberos user to revoke and regenerate the S3 secrets of any other user. This is only possible if: * ozone.s3g.secret.http.enabled is set to true. The default value of this configuration is false. * The user configured in ozone.s3g.kerberos.principal is also configured in ozone.s3.administrators or ozone.administrators. Users are recommended to upgrade to Apache Ozone version 1.4.1 which disables the affected endpoint.

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 1.4.0 S3 Gateway has improper authentication that allows any Kerberos-authenticated user to revoke and regenerate S3 secrets for any other user, due to insufficient authorization checks on an HTTP endpoint when specific configuration conditions are met.

MitigationUpgrade to Apache Ozone 1.4.1 which disables the vulnerable endpoint, and verify that ozone.s3g.secret.http.enabled remains false or is disabled if previously enabled.

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.4.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Ozone version
    Run 'ozone version' or check the RPM/Docker image version to confirm the installed Apache Ozone version is 1.4.0
    Affected if Version is exactly 1.4.0
  2. Verify S3 Gateway is deployed
    Check if the S3 Gateway component (ozone-s3g) is running: use 'kubectl get pods' for Kubernetes or 'ps aux | grep s3g' for standalone installations
    Affected if S3 Gateway process is running
  3. Check S3 secret HTTP configuration
    Inspect the Ozone configuration for property 'ozone.s3g.secret.http.enabled' in ozone-site.xml or via 'ozone getconf -confkey ozone.s3g.secret.http.enabled'
    Affected if The value is set to true or the property is missing (defaults to enabled in 1.4.0)
  4. Confirm Kerberos authentication is active
    Check ozone-site.xml for security configuration: look for 'ozone.security.authentication' set to 'kerberos' or verify keytab-based authentication is configured for S3 Gateway
    Affected if Kerberos authentication is enabled for the S3 Gateway

You are affected if running Apache Ozone 1.4.0 with S3 Gateway enabled and the ozone.s3g.secret.http.enabled configuration is not explicitly set to false, allowing any Kerberos-authenticated user to manipulate another user's S3 secrets via the HTTP endpoint.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Apache Ozone 1.4.1 which disables the vulnerable endpoint, and verify that ozone.s3g.secret.http.enabled remains false or is disabled if previously enabled.

Recommended fix High confidence

Apache Ozone 1.4.1

  1. Download Apache Ozone 1.4.1 from the official Apache Ozone distribution (https://ozone.apache.org/downloads/)
  2. Stop all Ozone services (om, scm, s3g, datanode) gracefully
  3. Back up your Ozone metadata and configuration files
  4. Replace the Ozone installation with version 1.4.1 files
  5. Restore your configuration files (or verify ozone.s3g.secret.http.enabled is not set to true)
  6. Start the Ozone services in the correct order: SCM → OM → DataNodes → S3Gateway
  7. Verify the S3 Gateway is operational and the vulnerable endpoint is disabled
Caveat The affected endpoint is disabled in 1.4.1; if you required ozone.s3g.secret.http.enabled functionality, you will lose that capability until a proper authenticated solution is available

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

Fix this in Ozone Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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