Apache Ozone security advisories
Security information for Apache Ozone
Reporting
Do you want disclose a potential security issue for Apache Ozone? Send your report to the Apache Ozone Security Team.
Advisories
This section is experimental: it provides advisories since 2023 and may lag behind the official CVE publications. If you have any feedback on how you would like this data to be provided, you are welcome to reach out on our public mailinglist or privately on security@apache.org
Improper authentication when generating S3 secrets
CVE-2024-45106 [CVE] [CVE json] [OSV json]
Last updated: 2024-12-03T09:06:21.271Z
Affected
- Apache Ozone at 1.4.0
Description
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.
References
Credits
- Ethan Rose (reporter)
- Ivan Zlenko (remediation developer)
Missing mutual TLS authentication in one of the service internal Ozone Storage Container Manager endpoints
CVE-2023-39196 [CVE] [CVE json] [OSV json]
Last updated: 2024-02-07T12:56:26.948Z
Affected
- Apache Ozone from 1.2.0 through 1.3.0
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.
References
Unauthenticated access to Ozone Recon HTTP endpoints
CVE-2021-41532 [CVE] [CVE json] [OSV json]
Last updated: 2021-11-19T09:13:58.824Z
Affected
- Apache Ozone from Everglades (1.1.0) through 1.1.0
Description
In Apache Ozone before 1.2.0, Recon HTTP endpoints provide access to OM, SCM and Datanode metadata. Due to a bug, any unauthenticated user can access the data from these endpoints.
References
Credits
- Apache Ozone would like to thank Ethan Rose for reporting this issue.
Owners of the S3 tokens are not validated
CVE-2021-39236 [CVE] [CVE json] [OSV json]
Last updated: 2021-11-19T09:13:11.634Z
Affected
- Apache Ozone from 1.0 through 1.0
Description
In Apache Ozone before 1.2.0, Authenticated users with valid Ozone S3 credentials can create specific OM requests, impersonating any other user.
References
Credits
- Apache Ozone would like to thank Marton Elek for reporting this issue.
Access mode of block tokens are not enforced
CVE-2021-39235 [CVE] [CVE json] [OSV json]
Last updated: 2021-11-19T09:11:44.999Z
Affected
- Apache Ozone from 1.0 through 1.0
Description
In Apache Ozone before 1.2.0, Ozone Datanode doesn’t check the access mode parameter of the block token. Authenticated users with valid READ block token can do any write operation on the same block.
References
Credits
- Apache Ozone would like to thank Marton Elek for reporting this issue.
Raw block data can be read bypassing ACL/authorization
CVE-2021-39234 [CVE] [CVE json] [OSV json]
Last updated: 2021-11-19T09:10:52.636Z
Affected
- Apache Ozone from 1.1 through 1.1
Description
In Apache Ozone versions prior to 1.2.0, Authenticated users knowing the ID of an existing block can craft specific request allowing access those blocks, bypassing other security checks like ACL.
References
Credits
- Apache Ozone would like to thank Marton Elek for reporting this issue.
Container-related datanode operations can be called without authorization
CVE-2021-39233 [CVE] [CVE json] [OSV json]
Last updated: 2021-11-19T09:10:07.173Z
Affected
- Apache Ozone from 1.1 through 1.1
Description
In Apache Ozone versions prior to 1.2.0, Container related Datanode requests of Ozone Datanode were not properly authorized and can be called by any client.
References
Credits
- Apache Ozone would like to thank Marton Elek for reporting this issue.
Missing admin check for SCM related admin commands
CVE-2021-39232 [CVE] [CVE json] [OSV json]
Last updated: 2021-11-19T09:09:30.310Z
Affected
- Apache Ozone from 1.0 through 1.0
Description
In Apache Ozone versions prior to 1.2.0, certain admin related SCM commands can be executed by any authenticated users, not just by admins.
References
Credits
-
Apache Ozone would like to thank Wei-Chiu Chuang for reporting this issue.
Missing authentication/authorization on internal RPC endpoints
CVE-2021-39231 [CVE] [CVE json] [OSV json]
Last updated: 2021-11-19T09:07:59.940Z
Affected
- Apache Ozone from 1.0 through 1.0
Description
In Apache Ozone versions prior to 1.2.0, Various internal server-to-server RPC endpoints are available for connections, making it possible for an attacker to download raw data from Datanode and Ozone manager and modify Ratis replication configuration.
References
Credits
- Apache Ozone would like to thank Marton Elek for reporting this issue.
Original block tokens are persisted and can be retrieved
CVE-2021-36372 [CVE] [CVE json] [OSV json]
Last updated: 2024-01-31T09:17:30.555Z
Affected
- Apache Ozone from 1.1 through 1.1
Description
In Apache Ozone versions prior to 1.2.0, Initially generated block tokens are persisted to the metadata database and can be retrieved with authenticated users with permission to the key. Authenticated users may use them even after access is revoked.
References
Credits
- Apache Ozone would like to thank Marton Elek for reporting this issue.
Ozone S3 Gateway allows bucket and key access to non authenticated users
CVE-2020-17517 [CVE] [CVE json] [OSV json]
Last updated: 2021-04-27T16:36:35.505Z
Affected
- Apache Ozone from Apache Ozone through 1.0.0
Description
The S3 buckets and keys in a secure Apache Ozone Cluster must be inaccessible to anonymous access by default. The current security vulnerability allows access to keys and buckets through a curl command or an unauthenticated HTTP request. This enables unauthorized access to buckets and keys thereby exposing data to anonymous clients or users. This affected Apache Ozone prior to the 1.1.0 release.
References
Credits
- Apache Ozone would like to thank Kota Uenishi for reporting this issue.