CVE-2022-34917: A security vulnerability has been identified in Apache Kafka.
High CVSS 7.5
- CVE id
- CVE-2022-34917
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Apache Kafka Runtimes and servers |
>= 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 |
How to fix it
Upgrade Apache Kafka to the fixed release of the line you run: 2.8.2, 3.0.2, 3.1.2, 3.2.3.
- Upgrade Kafka (the apache/kafka or Confluent image tag) to the patched release, broker by broker.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.