How severe is CVE-2024-12744?

No CVSS score has been assigned to CVE-2024-12744 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-12744?

CVE-2024-12744 affects the following packages: com.amazon.redshift:redshift-jdbc42 (Maven). Ecosystems affected: Maven.

How do I fix CVE-2024-12744?

Update com.amazon.redshift:redshift-jdbc42 to 2.1.0.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-12744 is resolved across your whole dependency graph.

How do I detect CVE-2024-12744 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.amazon.redshift:redshift-jdbc42, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2024-12744 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2024-12744 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-12744 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-12744?

CVE-2024-12744 has an EPSS (Exploit Prediction Scoring System) score of 0.6%, placing it in the 48th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-12744?

CVE-2024-12744 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2024-12744 published, and has it been updated?

CVE-2024-12744 was published on December 24, 2024 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2024-12744 — redshift-jdbc42

CVE-2024-12744 is a SQL Injection vulnerability in com.amazon.redshift:redshift-jdbc42. A fix is available for com.amazon.redshift:redshift-jdbc42 — see the affected versions and patch details below.

SQL Injection in the Amazon Redshift JDBC Driver affecting v2.1.0.31

Also known asGHSA-8596-2jgr-ppj7

Published

Dec 24, 2024

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 5, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for CVE-2024-12744.

EPSS Exploitation Probability

via FIRST.org ↗

0.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs48th percentile — riskier than 48% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

☕com.amazon.redshift:redshift-jdbc42

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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 [email protected]. Please do not create a public GitHub issue.

[1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.amazon.redshift:redshift-jdbc42`	≥ 2.1.0.31&&< 2.1.0.32	2.1.0.32`com.amazon.redshift:redshift-jdbc42:2.1.0.32`

Affected Products

1 product · 1 configurations

Application

amazon web services redshift java database connectivity driveramazon

1 version

2.1.0.31

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.amazon.redshift:redshift-jdbc42, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.amazon.redshift:redshift-jdbc42 to 2.1.0.32 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-12744 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

### 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 a

O3 Security · Impact-Aware SCA

Is CVE-2024-12744 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVE-2024-12744 — redshift-jdbc42

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

Real-World Exposure

Description

Summary

Impact

Patches

Workarounds

References

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2024-12744 in your dependencies?