dbcve.org
Amazon Web Services Redshift Java Database Connectivity DriverDatabase / datastore · Amazon

CVE-2024-12744

HIGH · 8.0 CVSS v3.1 Published 2024-12-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A SQL injection vulnerability in the Amazon Redshift JDBC Driver v2.1.0.31 allows privilege escalation through the getSchemas, getTables, and getColumns Metadata APIs by injecting malicious SQL via these metadata retrieval methods.

MitigationUpgrade the Amazon Redshift JDBC Driver to version 2.1.0.32 or revert to version 2.1.0.30 to remediate the SQL injection vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Amazon Web Services Redshift Java Database Connectivity DriverDatabase / datastore
Affected:= 2.1.0.31

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the Amazon Redshift JDBC Driver JAR file
    Search for JAR files containing 'redshift' in the filename within your application deployment directories, lib folders, or classpath. Common naming patterns include redshift-jdbc*.jar or AmazonRedshift*.jar.
    Affected if A JAR file with 'redshift' in the name is present in the environment
  2. Identify the installed driver version
    Open the JAR file and inspect the MANIFEST.MF file (located in the META-INF folder) for the Implementation-Version or Specification-Version attribute. Alternatively, check the JAR filename itself if the version is embedded.
    Affected if The version listed is 2.1.0.31 exactly
  3. Check application code for vulnerable API calls
    Search source code for calls to DatabaseMetaData methods: getSchemas(), getTables(), or getColumns(). Search patterns include '.getSchemas', '.getTables', '.getColumns', or review JDBC metadata usage in database access layers.
    Affected if The application code invokes any of these three metadata methods against a Redshift database
  4. Review build dependency configuration
    Examine build files (pom.xml, build.gradle, requirements.txt, or similar) for the Amazon Redshift JDBC Driver dependency and verify the declared version.
    Affected if The dependency specifies version 2.1.0.31

You are affected if the Amazon Redshift JDBC Driver version 2.1.0.31 is in use AND your application calls getSchemas, getTables, or getColumns against a Redshift database.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the Amazon Redshift JDBC Driver to version 2.1.0.32 or revert to version 2.1.0.30 to remediate the SQL injection vulnerability.

Recommended fix High confidence

2.1.0.32

  1. 1. Download the Amazon Redshift JDBC Driver version 2.1.0.32 from the official AWS website or Maven Central repository
  2. 2. Locate the existing redshift-jdbc-driver-2.1.0.31.jar file in your application or environment
  3. 3. Replace the old driver JAR file with the new version 2.1.0.32
  4. 4. Rebuild or redeploy any Java applications that use the Redshift JDBC driver
  5. 5. Verify that applications connect to Amazon Redshift successfully after the upgrade
  6. 6. Test the getSchemas, getTables, and getColumns Metadata APIs to confirm the vulnerability is remediated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Amazon Web Services Redshift Java Database Connectivity Driver Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12744 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-12744 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data