high
8
CWE
89
Advisory Published
Advisory Published
Updated

CVE-2022-31197: SQL Injection in ResultSet.refreshRow() with malicious column names in pgjdbc

First published: Wed Aug 03 2022(Updated: )

### Impact _What kind of vulnerability is it? Who is impacted?_ 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. For example: ```sql CREATE TABLE refresh_row_example ( id int PRIMARY KEY, "1 FROM refresh_row_example; SELECT pg_sleep(10); SELECT * " int ); ``` This example has a table with two columns. The name of the second column is crafted to contain a statement terminator followed by additional SQL. Invoking the `ResultSet.refreshRow()` on a ResultSet that queried this table, e.g. `SELECT * FROM refresh_row`, would cause the additional SQL commands such as the `SELECT pg_sleep(10)` invocation to be executed. As the multi statement command would contain multiple results, it would not be possible for the attacker to get data directly out of this approach as the `ResultSet.refreshRow()` method would throw an exception. However, the attacker could execute any arbitrary SQL including inserting the data into another table that could then be read or any other DML / DDL statement. 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. ### Patches _Has the problem been patched? What versions should users upgrade to?_ Yes, versions 42.2.26, 42.3.7, and 42.4.1 have been released with a fix. ### Workarounds _Is there a way for users to fix or remediate the vulnerability without upgrading?_ Check that you are not using the `ResultSet.refreshRow()` method. If you are, ensure that the code that executes that method does not connect to a database that is controlled by an unauthenticated or malicious user. If your application only connects to its own database with a fixed schema with no DDL permissions, then you will not be affected by this vulnerability as it requires a maliciously crafted schema.

Credit: security-advisories@github.com security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
redhat/postgresql-jdbc<42.2.26
42.2.26
redhat/postgresql-jdbc<42.3.7
42.3.7
redhat/postgresql-jdbc<42.4.1
42.4.1
redhat/postgresql-jdbc<0:42.2.18-6.el9_1
0:42.2.18-6.el9_1
Postgresql Postgresql Jdbc Driver<42.2.26
Postgresql Postgresql Jdbc Driver>=42.3.0<42.3.7
Postgresql Postgresql Jdbc Driver=42.4.0
Postgresql Postgresql Jdbc Driver=42.4.0-rc1
Postgresql Postgresql Jdbc Driver=42.4.1-rc1
Debian Debian Linux=10.0
Fedoraproject Fedora=35
Fedoraproject Fedora=36
IBM Disconnected Log Collector<=v1.0 - v1.8.2
maven/org.postgresql:postgresql>=42.3.0<42.3.7
42.3.7
maven/org.postgresql:postgresql>=42.4.0<42.4.1
42.4.1
maven/org.postgresql:postgresql<42.2.26
42.2.26

Remedy

https://github.com/pgjdbc/pgjdbc/commit/739e599d52ad80f8dcd6efedc6157859b1a9d637

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is CVE-2022-31197?

    CVE-2022-31197 is a vulnerability in the PostgreSQL JDBC Driver (PgJDBC) that allows an attacker to exploit a miss escaping character issue in the `java.sql.ResultRow.refreshRow()` method.

  • What is the severity of CVE-2022-31197?

    CVE-2022-31197 has a severity level of high.

  • How does CVE-2022-31197 affect PostgreSQL JDBC Driver?

    CVE-2022-31197 affects the PgJDBC implementation's `java.sql.ResultRow.refreshRow()` method and its handling of column names.

  • Which versions of PostgreSQL JDBC Driver are affected by CVE-2022-31197?

    Versions 0:42.2.18-6.el9_1, 42.2.26, 42.3.7, and 42.4.1 of PostgreSQL JDBC Driver are affected by CVE-2022-31197.

  • How can I mitigate CVE-2022-31197?

    To mitigate CVE-2022-31197, update to version 42.4.1 (or later) of PostgreSQL JDBC Driver.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203