Search for packages
| purl | pkg:maven/org.postgresql/postgresql@42.1.2.jre6 |
| Vulnerability | Summary | Fixed by |
|---|---|---|
|
VCID-7p16-8nb5-kucz
Aliases: CVE-2022-21724 GHSA-v7wg-cpwc-24m4 |
Remote code execution vulnerability using plugin features pgjdbc is the offical PostgreSQL JDBC Driver. A security hole was found in the jdbc driver for postgresql database while doing security research. The system using the postgresql library will be attacked when attacker control the jdbc url or properties. pgjdbc instantiates plugin instances based on class names provided via `authenticationPluginClassName`, `sslhostnameverifier`, `socketFactory`, `sslfactory`, `sslpasswordcallback` connection properties. However, the driver does not verify if the class implements the expected interface before instantiating the class. This can lead to remote code execution loaded via arbitrary classes. |
Affected by 3 other vulnerabilities. Affected by 3 other vulnerabilities. |
|
VCID-hpc5-vtmd-gub5
Aliases: CVE-2022-26520 GHSA-727h-hrw8-jg8q |
Path traversal in org.postgresql:postgresql ** DISPUTED ** In pgjdbc before 42.3.3, an attacker (who controls the jdbc URL or properties) can call java.util.logging.FileHandler to write to arbitrary files through the loggerFile and loggerLevel connection properties. An example situation is that an attacker could create an executable JSP file under a Tomcat web root. 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. |
Affected by 1 other vulnerability. |
|
VCID-uzj4-puvz-zfgh
Aliases: GHSA-673j-qm5f-xpv8 GMS-2022-75 |
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') The connection properties for configuring a pgjdbc connection are not meant to be exposed to an unauthenticated attacker. While allowing an attacker to specify arbitrary connection properties could lead to a compromise of a system, that's a defect of an application that allows unauthenticated attackers that level of control. It's not the job of the pgjdbc driver to decide whether a given log file location is acceptable. End user applications that use the pgjdbc driver must ensure that filenames are valid and restrict unauthenticated attackers from being able to supply arbitrary values. That's not specific to the pgjdbc driver either, it would be true for any library that can write to the application's local file system. While we do not consider this a security issue with the driver, we have decided to remove the `loggerFile` and `loggerLevel` connection properties in the next release of the driver. Removal of those properties does not make exposing the JDBC URL or connection properties to an attacker safe and we continue to suggest that applications do not allow untrusted users to specify arbitrary connection properties. We are removing them to prevent misuse and their functionality can be delegated to `java.util.logging`. |
Affected by 1 other vulnerability. |
|
VCID-vdtn-ek54-nqh6
Aliases: CVE-2020-13692 GHSA-88cc-g835-76rp |
Improper Restriction of XML External Entity Reference PostgreSQL JDBC Driver (aka PgJDBC) before 42.2.13 allows XXE. |
Affected by 4 other vulnerabilities. |
| Vulnerability | Summary | Aliases |
|---|---|---|
| This package is not known to fix vulnerabilities. | ||