Covert Timing Channel Affecting postgresql-jdbc package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.7% (51st percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-POSTGRESQLJDBC-14088876
  • published21 Nov 2025
  • disclosed22 Sept 2025

Introduced: 22 Sep 2025

CVE-2025-59432  (opens in a new tab)
CWE-385  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 postgresql-jdbc.

NVD Description

Note: Versions mentioned in the description apply only to the upstream postgresql-jdbc package and not the postgresql-jdbc package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1