A security vulnerability has been identified in Apache Kafka. It affects all releases since 2.8.0. The vulnerability allows malicious unauthenticated clients to allocate large amounts of memory on brokers. This can lead to brokers hitting OutOfMemoryException and causing denial of service. Example scenarios: - Kafka cluster without authentication: Any clients able to establish a network connection to a broker can trigger the issue. - Kafka cluster with SASL authentication: Any clients able to establish a network connection to a broker, without the need for valid SASL credentials, can trigger the issue. - Kafka cluster with TLS authentication: Only clients able to successfully authenticate via TLS can trigger the issue. We advise the users to upgrade the Kafka installations to one of the 3.2.3, 3.1.2, 3.0.2, 2.8.2 versions.
oryginał ENCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HApache Kafka
APPApache2.8.0 – 2.8.2 (bez)3.0.0 – 3.0.2 (bez)3.1.0 – 3.1.2 (bez)3.2.0 – 3.2.3 (bez)
Powiązane podatności
Apache Kafka: brak walidacji podpisu JWT w domyślnej konfiguracji SASL/OAUTHBEARER
A possible security vulnerability has been identified in Apache Kafka. This requires access to a alterConfig t...
A possible arbitrary file read and SSRF vulnerability has been identified in Apache Kafka Client. Apache Kafka...
In CVE-2023-25194, we announced the RCE/Denial of service attack via SASL JAAS JndiLoginModule configuration i...
While an Apache Kafka cluster is being migrated from ZooKeeper mode to KRaft mode, in some cases ACLs will not...