CyberRota Analysis
AI-GeneratedThe vulnerability affects the SCRAM authentication mechanism in versions prior to 3.3, allowing attackers to exploit a TLS man-in-the-middle attack to downgrade secure connections from SCRAM-SHA-256-PLUS with channel binding to the less secure SCRAM-SHA-256. This downgrade can lead to unauthorized access or data interception due to the absence of channel binding, which is critical for maintaining the integrity of the authentication process. Organizations using affected versions should prioritize upgrading to version 3.3 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
SCRAM (Salted Challenge Response Authentication Mechanism) is part of the family of Simple Authentication and Security Layer (SASL, RFC 4422) authentication mechanisms. Prior to 3.3, a flaw in com.ongres.scram:scram-client and com.ongres.scram:scram-common allows an attacker capable of a TLS man-in-the-middle attack to silently downgrade a connection from SCRAM-SHA-256-PLUS with channel binding to standard SCRAM-SHA-256 without channel binding when TlsServerEndpoint processes an X.509 certificate using a modern signature algorithm such as Ed25519; getChannelBindingData() can return an empty byte array after NoSuchAlgorithmException, and the ScramClient builder treats that as absent channel-binding data. This issue is fixed in version 3.3.