Amazon JDBC Driver for Redshift SQL Injection via line comment generation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

10.0 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

EPSS

• CVE-2024-32888: 0.78% estimated exploitation activity in the next 30 days; percentile 55.91 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact 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. Patch This issue is patched in driver version 2.1.0.28. Workarounds Do not use the connection property preferQueryMode=simple. (NOTE: If you do not explicitly specify a query mode, then you are using the default of extended query mode and are not affected by this issue.) References Similar to finding in Postgres JDBC: https://github.com/pgjdbc/pgjdbc/security/advisories/GHSA-24rp-q3w6-vc56 If you have any questions or comments about this advisory, we ask that you contact AWS…

Published by the source

15 May 2024, 17:10 UTC

Last modified by the source

13 Jun 2025, 20:45 UTC

Source last checked

26 Oct 2026, 16:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-x3wm-hffr-chwm

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-32888

Advisory: Amazon JDBC Driver for Redshift SQL Injection via line comment generation
IDs: CVE-2024-32888, GHSA-x3wm-hffr-chwm
Record: https://patchnext.com/advisories/cve-2024-32888 (revision 1, source checked 26 Oct 2026, 16:39 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: com.amazon.redshift:redshift-jdbc42 2.1.0.28. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven com.amazon.redshift:redshift-jdbc42: affected < 2.1.0.28; fixed in 2.1.0.28

## Suggested inspection (read-only)
- Maven com.amazon.redshift:redshift-jdbc42: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on com.amazon.redshift:redshift-jdbc42.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x3wm-hffr-chwm (GitHub-reviewed advisory GHSA-x3wm-hffr-chwm lists affected ranges: Maven com.amazon.redshift:redshift-jdbc42 >=0 <2.1.0.28)

Commands are suggestions: review each one before running it.