CVE-2024-1597
Public on
Last Modified:
Description
A flaw was found in the PostgreSQL JDBC Driver. A SQL injection is possible when using the non-default connection property preferQueryMode=simple in combination with application code that has a vulnerable SQL that negates a parameter value.
Statement
The PostgreSQL JDBC Driver is not affected in the default query mode. Users that do not override the query mode are not impacted.
The described SQL injection vulnerability, while significant, is categorized as important rather than critical due to several factors. Firstly, the exploitation relies on specific conditions, including the use of a non-default query mode (preferQueryMode=simple) and the precise arrangement of user-controlled parameters within the SQL query. This limits the potential attack surface and reduces the likelihood of widespread exploitation across systems. Additionally, the vulnerability does not pose an immediate and severe risk of system compromise or data breach; rather, it enables attackers to manipulate SQL queries and potentially execute arbitrary commands within the context of the application's database. Furthermore, the vulnerability can be effectively mitigated by applying the provided patch or by avoiding the use of the vulnerable query mode, thus reducing the risk of exploitation.
Red Hat Satellite ships a PostgreSQL JDBC Driver which embeds into Candlepin. However, Candlepin doesn't directly utilize the PostgreSQL JDBC Driver and doesn't set PreferQueryMode. Therefore, although the affected component is shipped, the product impact is considered Low. This issue may be addressed in a future Satellite release.
Mitigation
Do not use the connection propertypreferQueryMode=simple. If you do not explicitly specify a query mode, then you are using the default of extended and are not impacted by this issue.
Additional Information
- This content is not included.Bugzilla 2266523: pgjdbc: PostgreSQL JDBC Driver allows attacker to inject SQL if using PreferQueryMode=SIMPLE
- Content from cwe.mitre.org is not included.CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- FAQ: Frequently asked questions about CVE-2024-1597
- Offline Security Data data is available for integration with other systems. See Offline Security Data API to get started.
External References
Content from www.cve.org is not included.https://www.cve.org/CVERecord?id=CVE-2024-1597
Content from nvd.nist.gov is not included.https://nvd.nist.gov/vuln/detail/CVE-2024-1597
Affected Packages and Issued Red Hat Security Errata
| Products / Services | Components | State | Errata |
|---|---|---|---|
| RHEL-8 based Middleware Containers | rh-sso-7/sso7-rhel8-operator-bundle | Fixed | RHSA-2024:1686 |
| RHEL-8 based Middleware Containers | rh-sso-7/sso76-openshift-rhel8 | Fixed | RHSA-2024:1686 |
| RHINT Camel-K 1.10.7 | pgjdbc | Fixed | RHSA-2024:5056 |
| RHOSS-1.33-RHEL-8 | openshift-serverless-1/logic-data-index-ephemeral-rhel8 | Fixed | RHSA-2024:4057 |
| RHOSS-1.33-RHEL-8 | openshift-serverless-1/logic-data-index-postgresql-rhel8 | Fixed | RHSA-2024:4057 |
| RHOSS-1.33-RHEL-8 | openshift-serverless-1/logic-jobs-service-ephemeral-rhel8 | Fixed | RHSA-2024:4057 |
| RHOSS-1.33-RHEL-8 | openshift-serverless-1/logic-jobs-service-postgresql-rhel8 | Fixed | RHSA-2024:4057 |
| RHOSS-1.33-RHEL-8 | openshift-serverless-1/logic-kn-workflow-cli-artifacts-rhel8 | Fixed | RHSA-2024:4057 |
| RHOSS-1.33-RHEL-8 | openshift-serverless-1/logic-operator-bundle | Fixed | RHSA-2024:4057 |
| RHOSS-1.33-RHEL-8 | openshift-serverless-1/logic-rhel8-operator | Fixed | RHSA-2024:4057 |
| RHOSS-1.33-RHEL-8 | openshift-serverless-1/logic-swf-builder-rhel8 | Fixed | RHSA-2024:4057 |
| RHOSS-1.33-RHEL-8 | openshift-serverless-1/logic-swf-devmode-rhel8 | Fixed | RHSA-2024:4057 |
| Red Hat Enterprise Linux 6 | postgresql-jdbc | Not affected | |
| Red Hat Enterprise Linux 7 | postgresql-jdbc | Not affected | |
| Red Hat Enterprise Linux 8 | postgresql-jdbc | Fixed | RHSA-2024:1435 |
| Red Hat Enterprise Linux 8 | libreoffice:flatpak/postgresql-jdbc | Will not fix | |
| Red Hat Enterprise Linux 8.2 Advanced Update Support | postgresql-jdbc | Fixed | RHSA-2024:2624 |
| Red Hat Enterprise Linux 8.2 Telecommunications Update Service | postgresql-jdbc | Fixed | RHSA-2024:2624 |
| Red Hat Enterprise Linux 8.2 Update Services for SAP Solutions | postgresql-jdbc | Fixed | RHSA-2024:2624 |
| Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support | postgresql-jdbc | Fixed | RHSA-2024:4375 |
| Red Hat Enterprise Linux 8.4 Telecommunications Update Service | postgresql-jdbc | Fixed | RHSA-2024:4375 |
| Red Hat Enterprise Linux 8.4 Update Services for SAP Solutions | postgresql-jdbc | Fixed | RHSA-2024:4375 |
| Red Hat Enterprise Linux 8.6 Advanced Mission Critical Update Support | postgresql-jdbc | Fixed | RHSA-2024:4402 |
| Red Hat Enterprise Linux 8.6 Telecommunications Update Service | postgresql-jdbc | Fixed | RHSA-2024:4402 |
| Red Hat Enterprise Linux 8.6 Update Services for SAP Solutions | postgresql-jdbc | Fixed | RHSA-2024:4402 |
| Red Hat Enterprise Linux 8.8 Extended Update Support | postgresql-jdbc | Fixed | RHSA-2024:3313 |
| Red Hat Enterprise Linux 9 | postgresql-jdbc | Fixed | RHSA-2024:1436 |
| Red Hat Enterprise Linux 9 | libreoffice:flatpak/postgresql-jdbc | Will not fix | |
| Red Hat Enterprise Linux 9.0 Extended Update Support | postgresql-jdbc | Fixed | RHSA-2024:1999 |
| Red Hat Enterprise Linux 9.2 Extended Update Support | postgresql-jdbc | Fixed | RHSA-2024:1649 |
| Red Hat Fuse 7 | pgjdbc | Not affected | |
| Red Hat Integration Camel Quarkus 2 | pgjdbc | Will not fix | |
| Red Hat JBoss Enterprise Application Platform 8 | org.postgresql-pgjdbc | Not affected | |
| Red Hat Process Automation 7 | pgjdbc | Will not fix | |
| Red Hat Satellite 6 | candlepin | Not affected | |
| Red Hat Virtualization 4 | postgresql-jdbc | Not affected | |
| Red Hat build of Apache Camel 4 for Quarkus 3 | pgjdbc | Will not fix | |
| Red Hat build of Apache Camel 4.4.1 for Spring Boot 3.2 | pgjdbc | Fixed | RHSA-2024:4884 |
| Red Hat build of Apache Camel for Spring Boot 3 | pgjdbc | Affected | |
| Red Hat build of Apicurio Registry 2 | pgjdbc | Not affected | |
| Red Hat build of Keycloak 24 | pgjdbc | Fixed | RHBA-2024:2108 |
| Red Hat build of OptaPlanner 8 | pgjdbc | Will not fix | |
| Red Hat build of Quarkus 2.13.9.SP2 | org.postgresql/postgresql | Fixed | RHSA-2024:1797 |
| Red Hat build of Quarkus 3.2.11.Final | org.postgresql/postgresql | Fixed | RHSA-2024:1662 |
Common Vulnerability Scoring System (CVSS) Score Details
Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authorities (CNA) source for its products and services (see Red Hat classifications ).
| CVSS v3 Score Breakdown | Red Hat | NVD |
|---|---|---|
| CVSS v3 Base Score | 9.8 | 9.8 |
| Attack Vector | Network | Network |
| Attack Complexity | Low | Low |
| Privileges Required | None | None |
| User Interaction | None | None |
| Scope | Unchanged | Unchanged |
| Confidentiality Impact | High | High |
| Integrity Impact | High | High |
| Availability Impact | High | High |
CVSS v3 Vector
Red Hat CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Frequently Asked Questions
Why is Red Hat's CVSS v3 score or Impact different from other vendors?
For more information, see https://access.redhat.com/solutions/762393.
My product is listed as "Under investigation" or "Affected", when will Red Hat release a fix for this vulnerability?
- "Under investigation" doesn't necessarily mean that the product is affected by this vulnerability. It only means that our Analysis Team is still working on determining whether the product is affected and how it is affected.
- "Affected" means that our Analysis Team has determined that this product is affected by this vulnerability and might release a fix to address this in the near future.
What can I do if my product is listed as "Will not fix"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Upgrade to a supported product version that includes a fix for this vulnerability (recommended).
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
What can I do if my product is listed as "Fix deferred"?
Available options depend mostly on the Impact of the vulnerability and the current Life Cycle phase of your product. Overall, you have the following options:
- Apply a mitigation (if one exists).
- Open a This content is not included.support case to request a prioritization of releasing a fix for this vulnerability.
- Red Hat Engineering focuses on addressing high-priority issues based on their complexity or limited lifecycle support. Therefore, lower-priority issues will not receive immediate fixes.
What is a mitigation?
I have a Red Hat product but it is not in the above list, is it affected?
Why is my security scanner reporting my product as vulnerable to this vulnerability even though my product version is fixed or not affected?
Not sure what something means? Check out our Security Glossary.