CVE-2024-3288810.0CriticalCWE-89

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

aws · amazon-redshift-jdbc-driver

Affected: aws amazon-redshift-jdbc-driver · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.8%probability of exploitation in the next 30 days

56th percentile

050100

Higher than 56% of scored CVEs

10.0CriticalCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

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.)

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

aws · amazon-redshift-jdbc-driver< 2.1.0.28

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: SQL Injection
Vendor: aws
Published: May 2024
Band: Unlikely (under 1%), May 2024

CoverageNo articles yet

No CyberSIXT article names CVE-2024-32888 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.