Skip to content
Fencer Vulns
high 7.5

CVE-2022-34917 json

Unauthenticated clients may cause OutOfMemoryError on Apache Kafka Brokers

published 2022-09-20 4 y ago modified 2026-09-08 2 mo ago also BIT-kafka-2022-34917 , EUVD-2022-6777 , GHSA-c9h3-c6qj-hh7q

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

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.

Patch / fix

  • maven org.apache.kafka:kafka 2.8.2, 3.0.2, 3.1.2, 3.2.3
  • bitnami kafka 2.8.2, 3.0.2, 3.1.2, 3.2.3
  • apache kafka 2.8.2, 3.0.2, 3.1.2, 3.2.3

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-34917 updated cvss 7.5

Kafka: Unauthenticated clients may cause OutOfMemoryError on brokers

  • Red Hat AMQ Streams 2.2.0
    fixed: vendor fix RHSA-2022:6819
  • Red Hat build of Quarkus kafka
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
17 mo ago

Exploit prediction

1.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
maven org.apache.kafka:kafka
>=2.8.0, <2.8.2
>=3.0.0, <3.0.2
>=3.1.0, <3.1.2
>=3.2.0, <3.2.3
2.8.2
3.0.2
3.1.2
3.2.3
bitnami kafka
>=2.8.0, <2.8.2
>=3.0.0, <3.0.2
>=3.1.0, <3.1.2
>=3.2.0, <3.2.3
2.8.2
3.0.2
3.1.2
3.2.3

Affected products

  • Apache Software Foundation Apache Kafka

Classification

Weakness
  • CWE-789 Memory Allocation with Excessive Size Value
  • CWE-400 Uncontrolled Resource Consumption
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.