Skip to content

Duplicate Advisory: SQL injection in pgjdbc

Critical severity GitHub Reviewed Published Feb 19, 2024 to the GitHub Advisory Database • Updated Jun 10, 2024
Withdrawn This advisory was withdrawn on Feb 21, 2024

Package

maven org.postgresql:postgresql (Maven)

Affected versions

>= 42.7.0, < 42.7.2
>= 42.6.0, < 42.6.1
>= 42.5.0, < 42.5.5
>= 42.4.0, < 42.4.4
>= 42.3.0, < 42.3.9
< 42.2.8

Patched versions

42.7.2
42.6.1
42.5.5
42.4.4
42.3.9
42.2.8

Description

Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-24rp-q3w6-vc56. This link is maintained to preserve external references.

Original Description

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.

References

Published by the National Vulnerability Database Feb 19, 2024
Published to the GitHub Advisory Database Feb 19, 2024
Reviewed Feb 21, 2024
Withdrawn Feb 21, 2024
Last updated Jun 10, 2024

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Weaknesses

CVE ID

No known CVE

GHSA ID

GHSA-xfg6-62px-cxc2

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.