Описание
Apache Kafka vulnerability can lead to brokers hitting OutOfMemoryException, causing Denial of Service
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.
Ссылки
- https://nvd.nist.gov/vuln/detail/CVE-2022-34917
- https://github.com/apache/kafka/commit/14951a83e3fdead212156e5532359500d72f68bc
- https://github.com/apache/kafka/commit/2bfa24b2bd416e7b8c4a0c566b984c43904fdecb
- https://github.com/apache/kafka/commit/aaceb6b79bfcb1d32874ccdbc8f3138d1c1c00fb
- https://github.com/apache/kafka/commit/c1295662768e64b4467e27c3d5158f95f2307657
- https://issues.apache.org/jira/browse/KAFKA-14063
- https://kafka.apache.org/cve-list
- https://kafka.apache.org/cve-list#CVE-2022-34917
Пакеты
org.apache.kafka:kafka
>= 2.8.0, < 2.8.2
2.8.2
org.apache.kafka:kafka
>= 3.0.0, < 3.0.2
3.0.2
org.apache.kafka:kafka
>= 3.1.0, < 3.1.2
3.1.2
org.apache.kafka:kafka
>= 3.2.0, < 3.2.3
3.2.3
Связанные уязвимости
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.
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.
A security vulnerability has been identified in Apache Kafka. It affec ...
Уязвимость диспетчера сообщений Apache Kafka, связанная с неограниченным распределением ресурсов, позволяющая нарушителю вызвать отказ в обслуживании