Apache

Ozone

11 vulnerabilities found.

Hinweis: Diese Liste kann unvollständig sein. Daten werden ohne Gewähr im Ursprungsformat bereitgestellt.
  • EPSS 0.23%
  • Published 03.12.2024 10:15:05
  • Last modified 01.07.2025 20:29:26

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

  • EPSS 0.12%
  • Published 07.02.2024 13:15:07
  • Last modified 13.02.2025 17:16:50

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

  • EPSS 1.72%
  • Published 19.11.2021 10:15:08
  • Last modified 21.11.2024 06:18:58

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

  • EPSS 0.71%
  • Published 19.11.2021 10:15:08
  • Last modified 21.11.2024 06:18:58

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.

  • EPSS 1.63%
  • Published 19.11.2021 10:15:08
  • Last modified 21.11.2024 06:18:58

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.

  • EPSS 0.27%
  • Published 19.11.2021 10:15:08
  • Last modified 21.11.2024 06:18:58

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.

  • EPSS 0.5%
  • Published 19.11.2021 10:15:08
  • Last modified 21.11.2024 06:18:58

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.

Exploit
  • EPSS 0.64%
  • Published 19.11.2021 10:15:08
  • Last modified 21.11.2024 06:18:58

In Apache Ozone before 1.2.0, Authenticated users with valid Ozone S3 credentials can create specific OM requests, impersonating any other user.

  • EPSS 1.28%
  • Published 19.11.2021 10:15:08
  • Last modified 21.11.2024 06:26:21

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.

  • EPSS 0.63%
  • Published 19.11.2021 10:15:07
  • Last modified 21.11.2024 06:13:37

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.