CVE-2025-59432

libscram-java: SCRAM (Salted Challenge Response Authentication Mechanism) is part of the family of Simple Authentication and Securit...

CVE-2025-59432 is fixed in 2 products on 1 platform, first by DEBIAN-CVE-2025-59432, released September 22, 2025. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
n/a
No vendor severity
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0070
53rd percentile

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.

Where it's fixed

ProductFixed inFixReleased
Linux
libscram-java · Debian 14 3.2-1 DEBIAN-CVE-2025-59432 Sep 22, 2025
ongres-scram · opensuse-leap 15.6 2.1-150400.8.5.1 SUSE-SU-2025:4054-1 Nov 11, 2025
ongres-scram · opensuse-leap 16.0 3.1-160000.3.1 OPENSUSE-SU-2025:20059-1 Nov 19, 2025
ongres-scram · sles 15.6 2.1-150400.8.5.1 SUSE-SU-2025:4054-1 Nov 11, 2025
ongres-scram · sles 15.7 2.1-150400.8.5.1 SUSE-SU-2025:4054-1 Nov 11, 2025
ongres-scram · sles 16.0 3.1-160000.3.1 SUSE-SU-2025:21016-1 Nov 19, 2025

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.