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 vendors 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
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Postgresql_jdbc_driver | Postgresql | 42.1.0 (including) | 42.1.4 (including) |
| Postgresql_jdbc_driver | Postgresql | 42.3.0 (including) | 42.3.3 (excluding) |
| Red Hat Fuse 7.11 | RedHat | jdbc-postgresql | * |
| RHINT Service Registry 2.3.0 GA | RedHat | jdbc-postgresql | * |
| RHPAM 7.13.1 async | RedHat | jdbc-postgresql | * |
| Libpgjava | Ubuntu | bionic | * |
| Libpgjava | Ubuntu | impish | * |
| Libpgjava | Ubuntu | trusty | * |
| Libpgjava | Ubuntu | upstream | * |
| Libpgjava | Ubuntu | xenial | * |