[<prev] [day] [month] [year] [list]
Message-ID: <CAMVt_AwsEegeGHs7S8kEUxyyik1udHOyto+7-R6THm3X8=yfog@mail.gmail.com>
Date: Wed, 18 Dec 2024 18:52:45 +0530
From: Manikumar <manikumar@...che.org>
To: oss-security@...ts.openwall.com
Subject: CVE-2024-56128: Apache Kafka: SCRAM authentication vulnerable to
replay attacks when used without encryption
Severity: low
Affected versions:
- Apache Kafka 0.10.2.0 before 3.7.2
- Apache Kafka 3.8.0
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.
Credit:
Tim Fox (timvolpe@...il.com) (finder)
Vikas Singh <vikas@...fluent.io> (remediation developer)
References:
https://datatracker.ietf.org/doc/html/rfc5802https://datatracker.ietf.org/doc/html/rfc5802#section-9https://kafka.apache.org/documentation/#security_sasl_scram_securityhttps://kafka.apache.org/https://www.cve.org/CVERecord?id=CVE-2024-56128
Powered by blists - more mailing lists
Please check out the
Open Source Software Security Wiki, which is counterpart to this
mailing list.
Confused about mailing lists and their use?
Read about mailing lists on Wikipedia
and check out these
guidelines on proper formatting of your messages.
