pgjdbc is the offical PostgreSQL JDBC Driver. A security hole was found in the jdbc driver for postgresql database while doing security res…
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 did not verify if the class implements the expected interface before instantiating the class. This can lead to code execution loaded via arbitrary classes. Users using plugins are advised to upgrade. There are no known workarounds for this issue.
The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.
https://cwe.mitre.org/data/definitions/665.html →Open in CWE collection →The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
https://capec.mitre.org/data/definitions/26.html →Open in CAPEC collection →This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.
https://capec.mitre.org/data/definitions/29.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| libpgjava | Tracked | |
| libpgjava | Tracked | |
| libpgjava | Tracked | |
| libpgjava | Tracked | |
| libpgjava | Tracked | |
| libpgjava | Tracked | |
| libpgjava | Tracked | |
| libpgjava | Tracked | |
| libpgjava | Tracked | |
| libpgjava | Tracked | |
| libpgjava | Tracked | |
| libpgjava | Tracked | |
| libpgjava | Tracked | |
| postgresql-jdbc | Tracked | |
| postgresql-jdbc-javadoc | Tracked | |
| debian_linux | * | Tracked |
| fedora | * | Tracked |
| postgresql_jdbc_driver | * | Tracked |
| quarkus | * | Tracked |