Bug#1150330: marked as pending in libpostgresql-jdbc-java

[Christoph Berg]

Control: tag -1 pending

Hello,

Bug #1150330 in libpostgresql-jdbc-java reported by you has been fixed in the
Git repository and is awaiting an upload. You can see the commit
message below and you can check the diff of the fix at:

https://salsa.debian.org/java-team/libpostgresql-jdbc-java/-/commit/2a969c513914b30805ec2fe82f78d769250f0f89

------------------------------------------------------------------------
New upstream version 42.7.14. (Closes: #1150330)

  + CVE-2026-107315: versions 42.7.4 through 42.7.13 pad 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.setObject with a ByteStreamWriter, CopyIn.writeToCopy,
    PGCopyOutputStream.write, LargeObject.write, or Blob.setBytes. The
    driver accepts these calls without an error. An attacker who can make
    the application store such a value and read it back can collect earlier
    traffic. Applications whose declared lengths always match their data are
    not affected. Versions 42.7.3 and earlier pad with zeros.
  + CVE-2026-107314: 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-256, and a partial exclusion such as
    requireAuth=!password,!md5, are enforced correctly. The property has no
    default value, so a deployment that does not set it is not affected.
    42.7.14 fixes the problem: such a connection is refused with SQLState
    08004, and a value without a method in it is rejected as invalid.
------------------------------------------------------------------------

(this message was generated automatically)
-- 
Greetings

https://bugs.debian.org/1150330