Timing Attack Vulnerability in SCRAM Authentication
SCRAM (Salted Challenge Response Authentication Mechanism) is part of the family of Simple Authentication and Security Layer (SASL, RFC 4422) authentication mechanisms. Prior to version 3.2, a timing attack vulnerability exists in the SCRAM Java implementation. The issue arises because Arrays.equals was used to compare secret values such as client proofs and server signatures. Since Arrays.equals performs a short-circuit comparison, the execution time varies depending on how many leading bytes match. This behavior could allow an attacker to perform a timing side-channel attack and potentially infer sensitive authentication material. All users relying on SCRAM authentication are impacted. This vulnerability has been patched in version 3.1 by replacing Arrays.equals with MessageDigest.isEqual, which ensures constant-time comparison.
References
-
https://github.com/ongres/scram/security/advisories/GHSA-3wfh-36rx-9537 x_refsource_CONFIRM
Affected products
- ==< 3.2
Matching in nixpkgs
pkgs.perlPackages.AuthenSCRAM
Salted Challenge Response Authentication Mechanism (RFC 5802)
pkgs.python312Packages.scramp
Implementation of the SCRAM authentication protocol
pkgs.python313Packages.scramp
Implementation of the SCRAM authentication protocol
pkgs.perl538Packages.AuthenSCRAM
Salted Challenge Response Authentication Mechanism (RFC 5802)
pkgs.perl540Packages.AuthenSCRAM
Salted Challenge Response Authentication Mechanism (RFC 5802)
Package maintainers
-
@stigtsp Stig Palmquist <stig@stig.io>