Skip to main content
← All vulnerabilities
CVE-2022-34917GHSA-C9H3-C6QJ-HH7QBIT-KAFKA-2022-34917

Unauthenticated clients may cause OutOfMemoryError on Apache Kafka Brokers

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 2.8.2, 3.0.2, 3.1.2, 3.2.3
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

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.

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  3. Record last updated

Affected versions

  • Apache Software Foundation Apache Kafka

    Apache Kafka 2.8.0 2.8.0, Apache Kafka 2.8.1 2.8.1, Apache Kafka 3.0.0 3.0.0, Apache Kafka 3.0.1 3.0.1, Apache Kafka 3.1.0 3.1.0, Apache Kafka 3.1.1 3.1.1, Apache Kafka 3.2.0 3.2.0, Apache Kafka 3.2.1 3.2.1

  • org.apache.kafka:kafkaMaven

    From 2.8.0 · fixed in 2.8.2

  • org.apache.kafka:kafkaMaven

    From 3.0.0 · fixed in 3.0.2

  • org.apache.kafka:kafkaMaven

    From 3.1.0 · fixed in 3.1.2

  • org.apache.kafka:kafkaMaven

    From 3.2.0 · fixed in 3.2.3

References 1

kafka.apache.org