Security readout for executives and security teams
Plain-English summary
Apache Kafka brokers can be forced to consume large amounts of memory by clients that can connect to them. This can crash brokers with OutOfMemoryException and disrupt Kafka-dependent applications. The main business risk is service outage, especially where brokers are reachable by unauthenticated or broadly trusted clients.
Executive priority
Treat this as a high-priority availability risk for Kafka-backed services. Prioritize externally reachable, shared, or weakly segmented clusters first. Upgrade during the next urgent maintenance window, or sooner if broker access is broad.
Technical view
CVE-2022-34917 is a CWE-789 denial-of-service issue in Apache Kafka 2.8.0 through 3.2.1. Clients with broker network access may allocate excessive broker memory. SASL deployments remain exposed before valid credentials are required; TLS client authentication limits triggering to successfully authenticated TLS clients. Fixed versions are 2.8.2, 3.0.2, 3.1.2, and 3.2.3.
Likely exposure
Kafka clusters running affected 2.8.x, 3.0.x, 3.1.x, or 3.2.x releases are exposed when clients can reach broker listener ports. Exposure is highest without authentication or with SASL-only authentication. TLS client authentication narrows exposure to authenticated TLS clients.
Exploitation context
The provided sources do not claim active exploitation, and the bundle marks KEV as false. The issue is network reachable, low complexity, unauthenticated in common configurations, and impacts availability only. No exploit details are needed to assess urgency.
Researcher notes
The bundle does not include code-level root cause, indicators, or proof-of-concept details. Validate exposure through version, listener reachability, and authentication mode. Avoid reproduction against production because the failure mode is broker memory exhaustion and service disruption.
Mitigation direction
- Upgrade Kafka to 3.2.3, 3.1.2, 3.0.2, or 2.8.2 as applicable.
- Restrict broker listener access to trusted client networks only.
- Review SASL deployments because valid SASL credentials are not required to trigger exposure.
- Prefer strong client authentication where operationally feasible, following Apache Kafka guidance.
- Monitor broker memory pressure and OutOfMemoryException events until upgraded.
Validation and detection
- Inventory all Kafka broker versions and compare against affected releases.
- Identify every broker listener reachable by unauthenticated or untrusted clients.
- Confirm whether each listener uses no auth, SASL, or TLS client authentication.
- Check broker logs and monitoring for OutOfMemoryException or unexplained restarts.
- Verify upgraded clusters report fixed Kafka versions after deployment.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-789: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2022-34917 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://kafka.apache.org/cve-listCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.