CVE-2024-1597 (Critical) detected in postgresql-42.3.7.jar

[mend-bolt-for-github]

CVE-2024-1597 - Critical Severity Vulnerability

Vulnerable Library - postgresql-42.3.7.jar

PostgreSQL JDBC Driver Postgresql

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

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

Path to vulnerable library: /modules/all/pom.xml

Dependency Hierarchy:

• webdocs-admin-0.1.0-SNAPSHOT.jar (Root Library)
  • ❌ postgresql-42.3.7.jar (Vulnerable Library)

Found in HEAD commit: 2cda59cc9ba15234ad74bb5750717c564aad3b18

Found in base branch: master

Vulnerability Details

pgjdbc, the PostgreSQL JDBC Driver, allows attacker to inject SQL if using PreferQueryMode=SIMPLE. Note this is not the default. In the default mode there is no vulnerability. A placeholder for a numeric value must be immediately preceded by a minus. There must be a second placeholder for a string value after the first placeholder; both must be on the same line. By constructing a matching string payload, the attacker can inject SQL to alter the query,bypassing the protections that parameterized queries bring against SQL Injection attacks. Versions before 42.7.2, 42.6.1, 42.5.5, 42.4.4, 42.3.9, and 42.2.8 are affected.

Publish Date: 2024-02-19

URL: CVE-2024-1597

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

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Origin: https://www.cve.org/CVERecord?id=CVE-2024-1597

Release Date: 2024-02-19

Fix Resolution: org.postgresql:postgresql:42.2.8,42.3.9,42.4.4,42.5.5,42.6.1,42.7.2

---

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.