Vulnerabilities · 2022 · Postgresql
CVE-2022-26520
Postgresql Jdbc Driver vulnerability
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
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
Affected products
Postgresql Jdbc Driver, Debian Linux. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Postgresql Jdbc Driver runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- jdbc.postgresql.org/documentation/changelog.html#version_42.3.3 · Vendor Advisory
- jdbc.postgresql.org/documentation/head/tomcat.html · Vendor Advisory
- github.com/pgjdbc/pgjdbc/pull/2454/commits/017b929977b4f85795f9ad2fa5de6e80978b8ccc · Patch
- github.com/pgjdbc/pgjdbc/security/advisories/GHSA-673j-qm5f-xpv8 · Third Party Advisory
- www.debian.org/security/2022/dsa-5196 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2022-26520
- cve.org/CVERecord?id=CVE-2022-26520
More vulnerabilities in Postgresql products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.