CVE-2022-26520 (High) detected in postgresql-42.2.20.jar, postgresql-42.2.23.jar
mend-for-github-com opened this issue · 0 comments
CVE-2022-26520 - High Severity Vulnerability
Vulnerable Libraries - postgresql-42.2.20.jar, postgresql-42.2.23.jar
postgresql-42.2.20.jar
PostgreSQL JDBC Driver Postgresql
Library home page: https://jdbc.postgresql.org
Path to vulnerable library: /ache/org.postgresql/postgresql/jars/postgresql-42.2.20.jar,/home/wss-scanner/.ivy2/cache/org.postgresql/postgresql/jars/postgresql-42.2.20.jar
Dependency Hierarchy:
- ❌ postgresql-42.2.20.jar (Vulnerable Library)
postgresql-42.2.23.jar
PostgreSQL JDBC Driver Postgresql
Library home page: https://jdbc.postgresql.org
Path to vulnerable library: /ache/org.postgresql/postgresql/jars/postgresql-42.2.23.jar,/home/wss-scanner/.ivy2/cache/org.postgresql/postgresql/jars/postgresql-42.2.23.jar
Dependency Hierarchy:
- ❌ postgresql-42.2.23.jar (Vulnerable Library)
Found in base branch: master
Vulnerability Details
** DISPUTED ** 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.
Publish Date: 2022-03-10
URL: CVE-2022-26520
CVSS 3 Score Details (9.8)
Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: Low
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: High
- Integrity Impact: High
- Availability Impact: High
Suggested Fix
Type: Upgrade version
Origin: https://security-tracker.debian.org/tracker/CVE-2022-26520
Release Date: 2022-03-10
Fix Resolution: 42.2.26