# CVE-2024-32888: Amazon JDBC Driver for Redshift SQL Injection via line comment generation

> SQL injection in Amazon Redshift JDBC driver when using non-default simple query mode, allowing attackers to read or modify database data.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 May 2024
- **Updated:** 12 Jun 2025
- **Also known as:** GHSA-x3wm-hffr-chwm

## What is CVE-2024-32888?

CVE-2024-32888 is a critical SQL injection vulnerability in aws amazon-redshift-jdbc-driver, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Amazon JDBC Driver for Redshift is a Type 4 JDBC driver that provides database connectivity through the standard JDBC application program interfaces (APIs) available in the Java Platform, Enterprise Editions. Prior to version 2.1.0.28, SQL injection is possible when using the non-default connection property `preferQueryMode=simple` in combination with application code which has a vulnerable SQL that negates a parameter value. There is no vulnerability in the driver when using the default, extended query mode. Note that `preferQueryMode` is not a supported parameter in Redshift JDBC driver, and is inherited code from Postgres JDBC driver. Users who do not override default settings to utilize this unsupported query mode are not affected. This issue is patched in driver version 2.1.0.28. As a workaround, do not use the connection property `preferQueryMode=simple`. (NOTE: Those who do not explicitly specify a query mode use the default of extended query mode and are not affected by this issue.)

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2024-32888?

2 open source packages ship an affected version, including com.amazon.redshift:redshift-jdbc42.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.amazon.redshift:redshift-jdbc42` | Maven | All versions | 2.1.0.28 |
| `com.amazon.redshift:redshift-jdbc42` | Maven | All versions | 2.1.0.28 |

## How do I fix CVE-2024-32888?

Upgrade com.amazon.redshift:redshift-jdbc42 to 2.1.0.28 or later.

## Is CVE-2024-32888 being exploited?

There is no known exploitation of CVE-2024-32888 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-32888 and fix it if it is affected.

What it is: CVE-2024-32888 is a critical SQL injection vulnerability in aws amazon-redshift-jdbc-driver, published on 15 May 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-32888 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.amazon.redshift:redshift-jdbc42 (Maven): affected all versions; fixed in 2.1.0.28
- com.amazon.redshift:redshift-jdbc42 (Maven): affected all versions; fixed in 2.1.0.28

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-32888/ (Markdown: https://insights.sbomify.com/CVE-2024-32888/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-32888
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-32888
- OSV: https://osv.dev/vulnerability/CVE-2024-32888

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-32888/
Summaries are generated and may contain mistakes; the official description above is the record.