dbcve.org
Redshift Odbc DriverApplication · Amazon

CVE-2024-12746

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 ODBC Driver v2.1.5.0 (Windows or Linux) allows a user to gain escalated privileges via the SQLTables or SQLColumns Metadata APIs. Users are recommended to upgrade to the driver version 2.1.6.0 or revert to driver version 2.1.4.0.

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 exists in the Amazon Redshift ODBC Driver versions prior to 2.1.6.0. The flaw resides in the SQLTables and SQLColumns Metadata APIs, which fail to properly sanitize inputs. An attacker can exploit this to inject malicious SQL statements and potentially escalate privileges within the database.

MitigationUpgrade the Amazon Redshift ODBC Driver to version 2.1.6.0 on all affected Windows and Linux systems, or downgrade to version 2.1.4.0 if the newer version is unavailable.

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
Redshift Odbc DriverApplication
Affected:= 2.1.5.0

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. Identify Amazon Redshift ODBC Driver installation
    Search for installed ODBC drivers on the system using the ODBC Data Source Administrator (Windows) or odbc.ini/odbcinst command (Linux). Look for 'Amazon Redshift' in the driver list.
    Affected if The Amazon Redshift ODBC Driver is present on the system
  2. Determine installed driver version
    Open the ODBC Data Source Administrator, select the Amazon Redshift driver, and check the version property. On Linux, run 'odbcinst -q -d' to list drivers and check associated .ini files for version information.
    Affected if The reported version is 2.1.5.0
  3. Verify vulnerable API usage
    Review application logs, database audit logs, or application code that connects to Amazon Redshift via ODBC. Look for calls to SQLTables or SQLColumns functions, which are the vulnerable metadata APIs.
    Affected if Applications use SQLTables or SQLColumns calls against the Redshift driver
  4. Compare against affected version range
    If the driver version is identified, compare it to the known affected range: versions prior to 2.1.6.0. Version 2.1.5.0 is explicitly listed as affected.
    Affected if Installed version is 2.1.5.0 or any version prior to 2.1.6.0

The environment is affected if the Amazon Redshift ODBC Driver version 2.1.5.0 (or any version prior to 2.1.6.0) is installed and applications use the SQLTables or SQLColumns metadata APIs.

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 ODBC Driver to version 2.1.6.0 on all affected Windows and Linux systems, or downgrade to version 2.1.4.0 if the newer version is unavailable.

Recommended fix High confidence

2.1.6.0

  1. Identify the current installed version of Amazon Redshift ODBC Driver on all affected systems (Windows or Linux)
  2. Download Amazon Redshift ODBC Driver version 2.1.6.0 from the official AWS website or GitHub releases
  3. Uninstall the current driver version 2.1.5.0 from all affected systems
  4. Install the new driver version 2.1.6.0 following standard AWS installation procedures
  5. Verify the driver version has been successfully updated to 2.1.6.0
  6. Test application connectivity to ensure the driver upgrade does not break existing functionality
  7. Ensure all applications using this driver are restarted to load the new version

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

Fix this in Redshift Odbc Driver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-12746 — 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-12746 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