What is CVE-2024-45106?

CVE-2024-45106 is a high-severity improper authentication vulnerability in org.apache.ozone:ozone (maven), affecting versions = 1.4.0. It is fixed in 1.4.1. The application does not adequately verify the identity of a user, device, or process before granting access.

How severe is CVE-2024-45106?

CVE-2024-45106 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.apache.ozone:ozone are affected by CVE-2024-45106?

org.apache.ozone:ozone (maven) versions = 1.4.0 is affected.

Is there a fix for CVE-2024-45106?

Yes. CVE-2024-45106 is fixed in 1.4.1. Upgrade to this version or later.

Is CVE-2024-45106 exploitable, and should I be worried?

Whether CVE-2024-45106 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2024-45106 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2024-45106 in org.apache.ozone:ozone

Q: How do I fix CVE-2024-45106?

Upgrade org.apache.ozone:ozone to 1.4.1 or later.

Summary

Apache Ozone: Improper authentication when generating S3 secrets

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.

Impact

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

CVE-2024-45106 has a CVSS score of 8.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.4.1); upgrading removes the vulnerable code path.

Affected versions

org.apache.ozone:ozone (= 1.4.0)

Security releases

org.apache.ozone:ozone → 1.4.1 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade org.apache.ozone:ozone to 1.4.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-45106? CVE-2024-45106 is a high-severity improper authentication vulnerability in org.apache.ozone:ozone (maven), affecting versions = 1.4.0. It is fixed in 1.4.1. The application does not adequately verify the identity of a user, device, or process before granting access.
How severe is CVE-2024-45106? CVE-2024-45106 has a CVSS score of 8.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.apache.ozone:ozone are affected by CVE-2024-45106? org.apache.ozone:ozone (maven) versions = 1.4.0 is affected.
Is there a fix for CVE-2024-45106? Yes. CVE-2024-45106 is fixed in 1.4.1. Upgrade to this version or later.
Is CVE-2024-45106 exploitable, and should I be worried? Whether CVE-2024-45106 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2024-45106 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2024-45106? Upgrade org.apache.ozone:ozone to 1.4.1 or later.