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
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Debian | — | Upgrade libpgjava | Aug 17, 2022 | Mar 10, 2022 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Mar 10, 2022 |
| Suse | — | Upgrade ongres-stringprep-javadocUpgrade postgresql-jdbc-javadocUpgrade ongres-stringprepUpgrade ongres-stringprep-saslprepUpgrade ongres-scram-javadocUpgrade postgresql-jdbcUpgrade ongres-scramUpgrade ongres-stringprep-codegeneratorUpgrade ongres-scram-clientUpgrade ongres-stringprep-parentUpgrade ongres-scram-parent | Oct 26, 2022 | Mar 10, 2022 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub