Skip to content

Apache Kafka vulnerability can lead to brokers hitting OutOfMemoryException, causing Denial of Service

High severity GitHub Reviewed Published Sep 21, 2022 to the GitHub Advisory Database • Updated May 8, 2024

Package

maven org.apache.kafka:kafka (Maven)

Affected versions

>= 2.8.0, < 2.8.2
>= 3.0.0, < 3.0.2
>= 3.1.0, < 3.1.2
>= 3.2.0, < 3.2.3

Patched versions

2.8.2
3.0.2
3.1.2
3.2.3

Description

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.

References

Published by the National Vulnerability Database Sep 20, 2022
Published to the GitHub Advisory Database Sep 21, 2022
Reviewed Sep 21, 2022
Last updated May 8, 2024

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

0.092%
(40th percentile)

Weaknesses

CVE ID

CVE-2022-34917

GHSA ID

GHSA-c9h3-c6qj-hh7q

Source code

No known source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.