<p>Upgrade <code>Debian:unstable</code> <code>libpgjava</code> to version 42.4.1-1 or higher.</p>

SQL Injection Affecting libpgjava package, versions <42.4.1-1

Snyk CVSS

Attack Complexity Low

User Interaction Required

Confidentiality High

Integrity High

Availability High

Threat Intelligence

EPSS 0.12% (47^th 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 ID SNYK-DEBIANUNSTABLE-LIBPGJAVA-2974406
published 5 Aug 2022
disclosed 3 Aug 2022

Report a new vulnerability Found a mistake?

Introduced: 3 Aug 2022

CVE-2022-31197 Open this link in a new tab CWE-89 Open this link in a new tab

How to fix?

Upgrade Debian:unstable libpgjava to version 42.4.1-1 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libpgjava package and not the libpgjava package as distributed by Debian. See How to fix? for Debian:unstable relevant fixed versions and status.

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 via their JDBC application may be under the control of an attacker. The attack requires the attacker to trick the user into executing SQL against a table name who's column names would contain the malicious SQL and subsequently invoke the refreshRow() method on the ResultSet. Note that the application's JDBC user and the schema owner need not be the same. A JDBC application that executes as a privileged user querying database schemas owned by potentially malicious less-privileged users would be vulnerable. In that situation it may be possible for the malicious user to craft a schema that causes the application to execute commands as the privileged user. Patched versions will be released as 42.2.26 and 42.4.1. Users are advised to upgrade. There are no known workarounds for this issue.