Apache Kafka: Allocation of Resources Without Limits or Throttling
CVE-2022-34917 is a high-severity allocation of resources without limits or throttling vulnerability in Apache Kafka from Apache, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Apache Kafka versions: Apache Kafka 2.8.0 2.8.0; Apache Kafka 2.8.1 2.8.1; Apache Kafka 3.0.0 3.0.0, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.58% chance of exploitation within 30 days, higher than 76% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Kafka to 2.8.2 or 3.0.2 or 3.1.2 or 3.2.3, whichever matches your release line, or a later version.
- Read the advisory on kafka.apache.org for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Apache | 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 | Not stated |
| Apache | Kafka | 2.8.0 up to, but not including, 2.8.2; 3.0.0 up to, but not including, 3.0.2; 3.1.0 up to, but not including, 3.1.2; 3.2.0 up to, but not including, 3.2.3 | 2.8.2, 3.0.2, 3.1.2, 3.2.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- NoneNothing can be modified.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | NVD |
| CVSS 3.1 | 7.5 | High | CISA (ADP) |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Allocation of Resources Without Limits or Throttling
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
How developers prevent this class of flaw
- Clearly specify the minimum and maximum expectations for capabilities, and dictate which behaviors are acceptable when resource allocation reaches limits.
- Limit the amount of resources that are accessible to unprivileged users. Set per-user limits for resources. Allow the system administrator to define these limits. Be careful to avoid CWE-410.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
More Allocation of Resources Without Limits or Throttling vulnerabilities (CWE-770)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Advisories
Other vulnerabilities in Apache Kafka
- 8.1 High severity
- 8.8 High severity
- 7.5 High severity
- 9.1 Critical severity
- 9.1 Critical severity
- 9.1 Critical severity
Recent Allocation of Resources Without Limits or Throttling vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
- 7.5 High severity
Spotted an error? Tell us.