cve.bz

CVE-2024-56128 apache kafka

5.3 mediumEPSS 0.8%Fix available

Medium (5.3) in apache kafka. EPSS 0.8% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.kafka:kafka_2.13 3.7.2, 3.8.1.

On this page
Incorrect Implementation of Authentication Algorithm in Apache Kafka's SCRAM implementation. Issue Summary: Apache Kafka's implementation of the Salted Challenge Response Authentication Mechanism (SCRAM) did not fully adhere to the requirements of RFC 5802 [1]. Specifically, as per RFC 5802, the server must verify that the nonce sent by the client in the second message matches the nonce sent by the server in its first message. However, Kafka's SCRAM implementation did not perform this validation. Impact: This vulnerability is exploitable only when an attacker has plaintext access to the SCRAM authentication exchange. However, the usage of SCRAM over plaintext is strongly discouraged as it is considered an insecure practice [2]. Apache Kafka recommends deploying SCRAM exclusively with TLS encryption to protect SCRAM exchanges from interception [3]. Deployments using SCRAM with TLS are not affected by this issue. How to Detect If You Are Impacted: If your deployment uses SCRAM authentication over plaintext communication channels (without TLS encryption), you are likely impacted. To check if TLS is enabled, review your server.properties configuration file for listeners property. If you have SASL_PLAINTEXT in the listeners, then you are likely impacted. Fix Details: The issue has been addressed by introducing nonce verification in the final message of the SCRAM authentication exchange to ensure compliance with RFC 5802. Affected Versions: Apache Kafka versions 0.10.2.0 through 3.9.0, excluding the fixed versions below. Fixed Versions: 3.9.0 3.8.1 3.7.2 Users are advised to upgrade to 3.7.2 or later to mitigate this issue. Recommendations for Mitigation: Users unable to upgrade to the fixed versions can mitigate the issue by: - Using TLS with SCRAM Authentication: Always deploy SCRAM over TLS to encrypt authentication exchanges and protect against interception. - Considering Alternative Authentication Mechanisms: Evaluate alternative authentication mechanisms, such as PLAIN, Kerberos or OAuth with TLS, which provide additional layers of security.

Severity

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
0.8% (unchanged from 0.8% a week ago; 0.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 58th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-12-18. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-303 Incorrect Implementation of Authentication Algorithm
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-56128 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-56128?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-56128?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-56128 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Kafkafrom 0.10.2.0 before 3.7.2
Apache Software Foundation Apache Kafka3.8.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-p7c9-8xx8-h74fMavenorg.apache.kafka:kafka_2.13>=0.10.2.0 <3.7.23.7.2
GHSA-p7c9-8xx8-h74fMavenorg.apache.kafka:kafka_2.13>=3.8.0 <3.8.13.8.1
GHSA-p7c9-8xx8-h74fMavenorg.apache.kafka:kafka_2.12>=0.10.2.0 <3.7.23.7.2
GHSA-p7c9-8xx8-h74fMavenorg.apache.kafka:kafka_2.12>=3.8.0 <3.8.13.8.1
GHSA-p7c9-8xx8-h74fMavenorg.apache.kafka:kafka_2.11>=0.10.2.0 <=2.4.1no fix published
GHSA-p7c9-8xx8-h74fMavenorg.apache.kafka:kafka_2.10>=0.10.2.0 <=0.10.2.2no fix published

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is marked with an Important severity because it compromises a fundamental security requirement of the SCRAM protocol as specified in RFC 5802 —the validation of nonces for ensuring message integrity and preventing replay attacks. Without proper nonce validation, an attacker with plaintext access to the SCRAM authentication exchange could manipulate or replay parts of the authentication process, potentially gaining unauthorized access or disrupting the integrity of authentication. While the use of plaintext communication for SCRAM is discouraged, many legacy systems or misconfigured deployments may still rely on it, making them directly susceptible.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.

ProductPackageStateAdvisory
Streams for Apache Kafka 2.9.1Fixed 2025-06-30RHSA-2025:9922
Streams for Apache Kafka 3.0.0Fixed 2025-08-01RHSA-2025:12511
Streams for Apache Kafka 3.1.0kafka_2.13Fixed 2025-12-16RHSA-2025:23417
Red Hat build of Debezium 2kafka_2.13Not affected
Red Hat Fuse 7kafka_2.13Out of support scope
Red Hat Fuse 7org.apache.kafka/kafka_2.12Not affected
Red Hat Integration Camel K 1org.apache.kafka/kafka_2.12Will not fix
Red Hat JBoss Enterprise Application Platform 7kafka_2.12Not affected
Red Hat JBoss Enterprise Application Platform 7kafka_2.13Not affected
Red Hat JBoss Enterprise Application Platform 8kafka_2.12Not affected
Red Hat JBoss Enterprise Application Platform 8kafka_2.13Not affected
Red Hat JBoss Enterprise Application Platform Expansion Packkafka_2.12Affected
Red Hat JBoss Enterprise Application Platform Expansion Packkafka_2.13Not affected
streams for Apache Kafkakafka_2.13Affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2024-56128.

Attack patterns (CAPEC)

  • CAPEC-90 Reflection Attack in Authentication Protocol Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON