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.
The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Kafka | Apache | 2.8.0 (including) | 2.8.2 (excluding) |
| Kafka | Apache | 3.0.0 (including) | 3.0.2 (excluding) |
| Kafka | Apache | 3.1.0 (including) | 3.1.2 (excluding) |
| Kafka | Apache | 3.2.0 (including) | 3.2.3 (excluding) |
| Red Hat AMQ Streams 2.2.0 | RedHat | kafka | * |