Unauthenticated clients may cause OutOfMemoryError on Apache Kafka Brokers
Apache Software Foundation Apache Kafka
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.kafka:kafka Maven |
|
|
Apache Software Foundation Apache Kafka
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.kafka:kafka Maven |
|
|
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.
From the CVE record · apache
Apache Kafka brokers can be forced to allocate large amounts of memory, potentially causing an OutOfMemoryException and denial of service. On clusters without authentication or with SASL authentication, any client that can connect to a broker can trigger the issue without valid credentials. On clusters with TLS authentication, a client must successfully authenticate via TLS.
Operators running Apache Kafka 2.8.0–2.8.1, 3.0.0–3.0.1, 3.1.0–3.1.1, or 3.2.0–3.2.2 should check their installations.