CVE-2024-12744
highpriority · track · 0EPSS 0.006 · 48 %ileEURUUSEPSS · scored 2026-10-27
A SQL injection in the Amazon Redshift JDBC Driver in v2.1.0.31 allows a user to gain escalated privileges via the getSchemas, getTables, or getColumns Metadata APIs. Users should upgrade to the driver version 2.1.0.32 or revert to driver version 2.1.0.30.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · medium–high · 6.1–8.8
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (4)
Products and version ranges known to be affected.
- amazon amazon web services redshift java database connectivity driver= 2.1.0.31nvdUScpe:2.3:a:amazon:amazon_web_services_redshift_java_database_connectivity_driver:*:*:*:*:*:*:*:*
- Maven com.amazon.redshift:redshift-jdbc422.1.0.31 → 2.1.0.32osvUSpkg:maven/com.amazon.redshift/redshift-jdbc42
advisories (1)
Vendor and ecosystem advisories describing this.
- GHSA-8596-2jgr-ppj7Amazon Redshift JDBC Driver vulnerable to SQL Injection2024-12-26ghsa · osvUS
### Summary A SQL injection in the Amazon Redshift JDBC Driver in v2.1.0.31 allows a user to gain escalated privileges via schema injection in the getSchemas, getTables, or getColumns Metadata APIs. Users should upgrade to the driver version 2.1.0.32 or revert to driver version 2.1.0.30. ### Impact A SQL injection is possible in the Amazon Redshift JDBC Driver, version 2.1.0.31, when leveraging metadata APIs to retrieve information about database schemas, tables, or columns. **Impacted versions:** Amazon Redshift JDBC Driver version 2.1.0.31. ### Patches The issue described above has been addressed in the Amazon Redshift JDBC Driver, version 2.1.0.32. The patch implemented in this version ensures that every metadata command input is sent to the Redshift server as part of a parameterized query, using either QUOTE_IDENT(string) or QUOTE_LITERAL(string). After processing all the inputs into quoted identifiers or literals, the metadata command is composed using these inputs and then executed on the server. ### Workarounds Use the previous version of the Amazon Redshift JDBC Driver, 2.1.0.30. ### References If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to [aws-security@amazon.com](mailto:aws-security@amazon.com). Please do not create a public GitHub issue. [1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting
also known as (4)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (9)
External citations — patches, advisories, analysis.
- https://access.redhat.com/security/cve/cve-2024-12744cnnvd
- https://github.com/aws/amazon-redshift-jdbc-driver/releases/tag/v2.1.0.32Patchcnnvd
- https://github.com/aws/amazon-redshift-jdbc-driver/security/advisories/GHSA-8596-2jgr-ppj7cnnvd
- https://aws.amazon.com/security/security-bulletins/AWS-2024-015/enisa_euvd
- https://github.com/aws/amazon-redshift-jdbc-driver/releases/tag/v2.1.0.32enisa_euvd
- https://github.com/aws/amazon-redshift-jdbc-driver/security/advisories/GHSA-8596-2jgr-ppj7enisa_euvd
- https://aws.amazon.com/security/security-bulletins/AWS-2024-015/Vendor Advisorynvd
- https://github.com/aws/amazon-redshift-jdbc-driver/releases/tag/v2.1.0.32nvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan