CVE-2024-56128
Apache Kafka SCRAM Implementation Authentication Weakness
Description
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.
INFO
Published Date :
Dec. 18, 2024, 2:15 p.m.
Last Modified :
June 20, 2025, 6:13 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
1.4
Exploitability Score :
3.9
Public PoC/Exploit Available at Github
CVE-2024-56128 has a 1 public PoC/Exploit available at Github.
Go to the Public Exploits tab to see the list.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-56128.
| URL | Resource |
|---|---|
| https://datatracker.ietf.org/doc/html/rfc5802 | Technical Description |
| https://datatracker.ietf.org/doc/html/rfc5802#section-9 | Technical Description |
| https://kafka.apache.org/documentation/#security_sasl_scram_security | Product |
| https://lists.apache.org/thread/84dh4so32lwn7wr6c5s9mwh381vx9wkw | Mailing List Vendor Advisory |
| http://www.openwall.com/lists/oss-security/2024/12/18/3 | Mailing List Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
A lightweight CLI tool written in Go for scanning Java (Maven) and Go (modules) project dependencies against the OSS Index vulnerability database. Outputs a clean, colorized ASCII box report with clickable links, severity-based coloring, and upgrade suggestions.
cve cve-scanning etree go java oss scanner vulnerability-scanners maven maven-pom pom
Go
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-56128 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-56128 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Initial Analysis by [email protected]
Jun. 20, 2025
Action Type Old Value New Value Added CWE NVD-CWE-Other Added CPE Configuration OR *cpe:2.3:a:apache:kafka:*:*:*:*:*:*:*:* versions from (including) 0.10.2.0 up to (excluding) 3.7.2 *cpe:2.3:a:apache:kafka:3.8.0:*:*:*:*:*:*:* Added Reference Type CVE: http://www.openwall.com/lists/oss-security/2024/12/18/3 Types: Mailing List, Third Party Advisory Added Reference Type Apache Software Foundation: https://datatracker.ietf.org/doc/html/rfc5802 Types: Technical Description Added Reference Type Apache Software Foundation: https://datatracker.ietf.org/doc/html/rfc5802#section-9 Types: Technical Description Added Reference Type Apache Software Foundation: https://kafka.apache.org/documentation/#security_sasl_scram_security Types: Product Added Reference Type Apache Software Foundation: https://lists.apache.org/thread/84dh4so32lwn7wr6c5s9mwh381vx9wkw Types: Mailing List, Vendor Advisory -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Dec. 18, 2024
Action Type Old Value New Value Added CVSS V3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N -
CVE Modified by af854a3a-2127-422b-91ae-364da2661108
Dec. 18, 2024
Action Type Old Value New Value Added Reference http://www.openwall.com/lists/oss-security/2024/12/18/3 -
New CVE Received by [email protected]
Dec. 18, 2024
Action Type Old Value New Value Added Description 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. Added CWE CWE-303 Added Reference https://datatracker.ietf.org/doc/html/rfc5802 Added Reference https://datatracker.ietf.org/doc/html/rfc5802#section-9 Added Reference https://kafka.apache.org/documentation/#security_sasl_scram_security Added Reference https://lists.apache.org/thread/84dh4so32lwn7wr6c5s9mwh381vx9wkw
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-56128 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-56128
weaknesses.