pgjdbc is an open source postgresql JDBC Driver. In affected versions a prepared statement using either PreparedStatement.setText(int, InputStream) or PreparedStatemet.setBytea(int, InputStream) will create a temporary file if the InputStream is larger than 2k. This will create a temporary file which is readable by other users on Unix like systems, but not MacOS. On Unix like systems, the systems temporary directory is shared between all users on that system. Because of this, when files and directories are written into this directory they are, by default, readable by other users on that same system. This vulnerability does not allow other users to overwrite the contents of these directories or files. This is purely an information disclosure vulnerability. Because certain JDK file system APIs were only added in JDK 1.7, this this fix is dependent upon the version of the JDK you are using. Java 1.7 and higher users: this vulnerability is fixed in 4.5.0. Java 1.6 and lower users: no patch is available. If you are unable to patch, or are stuck running on Java 1.6, specifying the java.io.tmpdir system environment variable to a directory that is exclusively owned by the executing user will mitigate this vulnerability.
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Postgresql_jdbc_driver | Postgresql | 42.2.0 (including) | 42.2.27 (excluding) |
| Postgresql_jdbc_driver | Postgresql | 42.3.0 (including) | 42.3.8 (excluding) |
| Postgresql_jdbc_driver | Postgresql | 42.4.0 (including) | 42.4.3 (excluding) |
| Postgresql_jdbc_driver | Postgresql | 42.5.0 (including) | 42.5.0 (including) |
| Postgresql_jdbc_driver | Postgresql | 42.5.0-rc1 (including) | 42.5.0-rc1 (including) |
| CEQ 2.13.2-1 | RedHat | jdbc-postgresql | * |
| Red Hat build of Quarkus | RedHat | * | |
| Red Hat build of Quarkus 2.7.7 | RedHat | jdbc-postgresql | * |
| Red Hat Enterprise Linux 8 | RedHat | postgresql-jdbc-0:42.2.14-2.el8 | * |
| Red Hat Enterprise Linux 9 | RedHat | postgresql-jdbc-0:42.2.27-1.el9 | * |
| Red Hat Fuse 7.12 | RedHat | jdbc-postgresql | * |
| Red Hat Satellite 6.12 for RHEL 8 | RedHat | candlepin-0:4.1.20-1.el8sat | * |
| Red Hat Satellite 6.13 for RHEL 8 | RedHat | candlepin-0:4.2.13-1.el8sat | * |
| Red Hat Virtualization 4 | RedHat | ovirt-ansible-collection | * |
| Red Hat Virtualization 4 | RedHat | ovirt-engine | * |
| Red Hat Virtualization 4 | RedHat | postgresql-jdbc | * |
| RHINT Camel-K-1.10.1 | RedHat | jdbc-postgresql | * |
| RHINT Camel-Q 2.7-1 | RedHat | jdbc-postgresql | * |
| RHINT Debezium 2.1.4 | RedHat | postgresql-jdbc | * |
| Libpgjava | Ubuntu | bionic | * |
| Libpgjava | Ubuntu | kinetic | * |
| Libpgjava | Ubuntu | lunar | * |
| Libpgjava | Ubuntu | mantic | * |
| Libpgjava | Ubuntu | trusty | * |
| Libpgjava | Ubuntu | xenial | * |
Resources such as files and directories may be inadvertently exposed through mechanisms such as insecure permissions, or when a program accidentally operates on the wrong object. For example, a program may intend that private files can only be provided to a specific user. This effectively defines a control sphere that is intended to prevent attackers from accessing these private files. If the file permissions are insecure, then parties other than the user will be able to access those files. A separate control sphere might effectively require that the user can only access the private files, but not any other files on the system. If the program does not ensure that the user is only requesting private files, then the user might be able to access other files on the system. In either case, the end result is that a resource has been exposed to the wrong party.