p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in libpgjava

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für libpgjava: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 7

  1. CVE-2026-107315

    Mittel · CVSS 5.3EPSS 0,2%Öffentlicher ExploitKeine Korrektur veröffentlicht

    pgjdbc pads a value shorter than its declared length with bytes of earlier statements (rather than zeros)

    pgjdbc, the PostgreSQL JDBC Driver, versions 42.7.4 through 42.7.13 pads a value that is shorter than its declared length with bytes left in its send buffer instead of zeros, and the server stores those bytes as part of the value. The bytes are messages the driver sent earlier on the same connection: SQL text and parameter values of recent statements, which on a pooled connection can come from other requests. Each padded value can carry up to 8192 bytes of this traffic, or 16320 bytes on a connection with GSS encryption. The padding happens when an application declares a length larger than the data it supplies, through PreparedStatement.setOb

    Veröffentlicht Aktualisiert
  2. CVE-2026-107314

    Mittel · CVSS 5.9EPSS 0,34%Keine Korrektur veröffentlicht

    pgjdbc does not enforce requireAuth when the value excludes every authentication method

    pgjdbc, the PostgreSQL JDBC Driver, versions 42.7.11 through 42.7.13 enforce no restriction when the requireAuth connection property excludes all six authentication methods the driver knows, for example requireAuth=!password,!md5,!gss,!sspi,!scram-sha-256,!none. The driver then accepts any method the server asks for, including cleartext password authentication. A value without a method in it, such as requireAuth=, (a single comma), is affected the same way. An attacker positioned between the application and its server can ask for cleartext password authentication and receive the database password. A positive list such as requireAuth=scram-sha

    Veröffentlicht Aktualisiert
  3. CVE-2026-54291

    Hoch · CVSS 8.2EPSS 0,24%Keine Korrektur veröffentlicht

    Silent channel-binding authentication downgrade via unsupported certificate algorithms

    pgjdbc is an open source postgresql JDBC Driver. In releases 42.7.4 through 42.7.11, channelBinding=require connections can be silently downgraded from SCRAM-SHA-256-PLUS with channel binding to plain SCRAM-SHA-256 without it, losing the man-in-the-middle protection the setting is meant to guarantee. An attacker who can intercept the TLS connection can trigger the downgrade with a certificate whose signature algorithm has no tls-server-end-point channel-binding hash, because the bundled com.ongres.scram:scram-client returns an empty byte array instead of failing and pgJDBC ScramAuthenticator checks only that the server advertised a PLUS mecha

    Veröffentlicht Aktualisiert
  4. CVE-2026-42198

    Hoch · CVSS 7.5EPSS 3,26%Keine Korrektur veröffentlicht

    pgjdbc: Unbounded PBKDF2 iterations in SCRAM authentication allows CPU exhaustion DoS

    pgjdbc is an open source postgresql JDBC Driver. From version 42.2.0 to before version 42.7.11, pgjdbc is vulnerable to a client-side denial of service during SCRAM-SHA-256 authentication. A malicious server can instruct the driver to perform SCRAM authentication with a very large iteration count. With a large enough value, the client spends an unbounded amount of CPU time inside PBKDF2 before authentication can fail. A single attempt ties up a CPU core. Repeated or concurrent attempts exhaust client CPU and can wedge connection pools. In affected versions, loginTimeout did not fully mitigate this problem. When loginTimeout expired, the calle

    Veröffentlicht Aktualisiert
  5. CVE-2025-49146

    Hoch · CVSS 8.2EPSS 0,49%Keine Korrektur veröffentlicht

    pgjdbc Client Allows Fallback to Insecure Authentication Despite channelBinding=require Configuration

    pgjdbc is an open source postgresql JDBC Driver. From 42.7.4 and until 42.7.7, when the PostgreSQL JDBC driver is configured with channel binding set to required (default value is prefer), the driver would incorrectly allow connections to proceed with authentication methods that do not support channel binding (such as password, MD5, GSS, or SSPI authentication). This could allow a man-in-the-middle attacker to intercept connections that users believed were protected by channel binding requirements. This vulnerability is fixed in 42.7.7.

    Veröffentlicht Aktualisiert
  6. CVE-2022-41946

    Mittel · CVSS 4.7EPSS 0,57%Keine Korrektur veröffentlicht

    TemporaryFolder on unix-like systems does not limit access to created files in pgjdbc

    pgjdbc is an open source postgresql JDBC Driver. In affected versions a prepared statement using either `PreparedStatement.setText(int, InputStream)` or `PreparedStatemet.setBytea(int, InputStream)` will create a temporary file if the InputStream is larger than 2k. This will create a temporary file which is readable by other users on Unix like systems, but not MacOS. On Unix like systems, the system's temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system. This vulnerability does not allow othe

    Veröffentlicht Aktualisiert
  7. CVE-2022-31197

    Hoch · CVSS 7.1EPSS 2,35%Keine Korrektur veröffentlicht

    SQL Injection in ResultSet.refreshRow() with malicious column names in pgjdbc

    PostgreSQL JDBC Driver (PgJDBC for short) allows Java programs to connect to a PostgreSQL database using standard, database independent Java code. The PGJDBC implementation of the `java.sql.ResultRow.refreshRow()` method is not performing escaping of column names so a malicious column name that contains a statement terminator, e.g. `;`, could lead to SQL injection. This could lead to executing additional SQL commands as the application's JDBC user. User applications that do not invoke the `ResultSet.refreshRow()` method are not impacted. User application that do invoke that method are impacted if the underlying database that they are querying

    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →