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 by replacing Arrays.equals with MessageDigest.isEqual, which ensures constant-time comparison.
Users should upgrade to version 3.2 or later to mitigate this issue.
Because the attack requires high precision and repeated attempts, the risk is limited, but the only reliable mitigation is to upgrade to a patched release (version 3.2 or later).
| Score | Percentile |
|---|---|
| 0.09% | 26.17% |
| Base score | Version | Severity | Vector |
|---|---|---|---|
| 6.6 | 4.0 | — |
|
| Type | Value |
|---|---|
| GHSA | GHSA-3wfh-36rx-9537 ↗ |
| CVE | CVE-2025-59432 ↗ |
Vulnerable version ranges and first patched releases as published by GitHub.
| Ecosystem | Package | Vulnerable range | First patched | Vulnerable functions |
|---|---|---|---|---|
| maven | com.ongres.scram:scram-common | < 3.2 | 3.2 | — |