CVE-2022-21724 (High) detected in postgresql-42.2.23.jar

[mend-bolt-for-github]

CVE-2022-21724 - High Severity Vulnerability

Vulnerable Library - postgresql-42.2.23.jar

PostgreSQL JDBC Driver Postgresql

Library home page: https://jdbc.postgresql.org/

Path to dependency file: /modules/admin/pom.xml

Path to vulnerable library: /modules/admin/pom.xml,/modules/document-generator/pom.xml

Dependency Hierarchy:

• ❌ postgresql-42.2.23.jar (Vulnerable Library)

Found in HEAD commit: 2cda59cc9ba15234ad74bb5750717c564aad3b18

Found in base branch: master

Vulnerability Details

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.

Publish Date: 2022-02-02

URL: CVE-2022-21724

CVSS 3 Score Details (7.0)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Local
  • Attack Complexity: High
  • Privileges Required: Low
  • User Interaction: None
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: High
  • Integrity Impact: High
  • Availability Impact: High

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: GHSA-v7wg-cpwc-24m4

Release Date: 2022-02-02

Fix Resolution: 42.2.23.jre6

---

Step up your Open Source Security Game with Mend here

[github-actions]

Thank you for opening an issue. If this issue is related to a bug, please follow the steps and provide the information outlined in the Troubleshooting Guide. Failure to follow these instructions may result in automatic closing of this issue.