Homepage
About Snyk

org.postgresql:postgresql@42.2.24.jre7 vulnerabilities

  • latest version

    42.7.3

  • latest non vulnerable version

    42.7.3

  • first published

    11 years ago

  • latest version published

    2 months ago

  • licenses detected

    • BSD-2-Clause
      [9.2-1002-jdbc4,9.4-1200-jdbc4); [9.4.1212,9.4.1212.jre6); [42.0.0,42.0.0.jre6); [42.1.0,42.1.0.jre7); [42.1.1,42.1.1.jre6); [42.1.2,42.1.2.jre6); [42.1.3,42.1.3.jre6); [42.1.4,42.1.4.jre6); [42.2.0,42.2.0.jre6); [42.2.1,42.2.1.jre6); [42.2.2,42.2.2.jre6); [42.2.3,42.2.3.jre6); [42.2.4,42.2.4.jre6); [42.2.5,42.2.5.jre6); [42.2.6,42.2.6.jre6); [42.2.7,42.2.7.jre6); [42.2.8,42.2.8.jre6); [42.2.9,42.2.9.jre6); [42.2.10,42.2.10.jre6); [42.2.11,42.2.11.jre6); [42.2.12,42.2.12.jre6); [42.2.13,)

  • package manager

    View on Maven Repository
Go back to all versions of this package
Report a new vulnerability Found a mistake?

Direct Vulnerabilities

Known vulnerabilities in the org.postgresql:postgresql package. This does not include vulnerabilities belonging to this package’s dependencies.

Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.
Fix for free
Vulnerability Vulnerable Version
  • C
SQL Injection

org.postgresql:postgresql is a Java JDBC 4.2 (JRE 8+) driver for PostgreSQL database.

Affected versions of this package are vulnerable to SQL Injection when using PreferQueryMode=SIMPLE, which is not the default setting. By passing in a numeric value placeholder immediately preceded by a minus and followed by a second placeholder for a string value, on the same line, an attacker can construct a payload that alters the parameterized query into which it is interpolated. This effectively bypasses the protections against SQL Injection that parameterized queries offer.

How to fix SQL Injection?

Upgrade org.postgresql:postgresql to version 42.2.28.jre7, 42.3.9, 42.4.4, 42.5.5, 42.6.1, 42.7.2 or higher.

[,42.2.28.jre7) [42.3.0,42.3.9) [42.4.0,42.4.4) [42.5.0,42.5.5) [42.6.0,42.6.1) [42.7.0,42.7.2)
  • M
Information Exposure

org.postgresql:postgresql is a Java JDBC 4.2 (JRE 8+) driver for PostgreSQL database.

Affected versions of this package are vulnerable to Information Exposure in the pgjdbc driver, which writes to the operating system's shared temp directory when the InputStream to either PreparedStatement.setText(int, InputStream) or PreparedStatemet.setBytea(int, InputStream) is larger than 2K. The temporary file is readable by other users. This is the default system behavior on Unix systems but not on MacOS.

NOTE: This vulnerability is only fixed for JDK 1.7. Systems using JDK 1.6 or below can work around the vulnerability by setting the environment variable java.io.tmpdir to a non-world-readable location.

How to fix Information Exposure?

Upgrade org.postgresql:postgresql to version 42.2.27, 42.3.8, 42.4.3, 42.5.1 or higher.

[42.2.0,42.2.27) [42.3.0,42.3.8) [42.4.0,42.4.3) [42.5.0,42.5.1)
  • H
SQL Injection

org.postgresql:postgresql is a Java JDBC 4.2 (JRE 8+) driver for PostgreSQL database.

Affected versions of this package are vulnerable to SQL Injection via the java.sql.ResultRow.refreshRow() function in jdbc/PgResultSet.java, due to insufficient escaping column names. An attacker with control of the underlying database can name a column with a string containing a semicolon or other statement terminator, then convince a user to run a query against the table with the compromised column, and then have the application run ResultSet.refreshRow(), to execute code.

NOTE:

  • An application that only connects to its own database with a fixed schema with no DDL permissions is not affected by this vulnerability.
  • Additionally, applications that do not invoke ResultSet.refreshRow() are not affected.

How to fix SQL Injection?

Upgrade org.postgresql:postgresql to version 42.2.26, 42.3.7, 42.4.1 or higher.

[,42.2.26) [42.3.0,42.3.7) [42.4.0,42.4.1)
  • H
Arbitrary Code Injection

org.postgresql:postgresql is a Java JDBC 4.2 (JRE 8+) driver for PostgreSQL database.

Affected versions of this package are vulnerable to Arbitrary Code Injection. DISPUTED

When an arbitrary filename is specified in the loggerFileName connection parameter jdbc:postgresql://localhost:5432/test?user=test&password=test&loggerLevel=DEBUG&loggerFile=./blah.jsp&<%Runtime.getRuntime().exec(request.getParameter("i"));%>, a valid JSP file is created and a Remote Code Execution could be performed.

Note: the vendor's position is that there is no pgjdbc vulnerability; instead, it is a vulnerability for any application to use the pgjdbc driver with untrusted connection properties.

How to fix Arbitrary Code Injection?

Upgrade org.postgresql:postgresql to version 42.3.3 or higher.

[42.1.0,42.3.3)
  • H
Remote Code Execution (RCE)

org.postgresql:postgresql is a Java JDBC 4.2 (JRE 8+) driver for PostgreSQL database.

Affected versions of this package are vulnerable to Remote Code Execution (RCE) when using certain plugin features. pgjdbc instantiates plugin instances based on class names provided via authenticationPluginClassName, sslhostnameverifier, socketFactory, sslfactory, and sslpasswordcallback connection properties.

However, the driver did not verify if the class implements the expected interface before instantiating the class.

How to fix Remote Code Execution (RCE)?

Upgrade org.postgresql:postgresql to version 42.2.25, 42.3.2 or higher.

[9.4.1208,42.2.25) [42.3.0,42.3.2)
Go back to all versions of this package