dbcve.org
Redshift ConnectorApplication · Amazon

CVE-2024-12745

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 Python Connector v2.1.4 allows a user to gain escalated privileges via the get_schemas, get_tables, or get_columns Metadata APIs. Users are recommended to upgrade to the driver version 2.1.5 or revert to driver version 2.1.3.

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 Python Connector version 2.1.4 within the Metadata APIs (get_schemas, get_tables, and get_columns). An attacker can exploit unsanitized input to inject malicious SQL statements, potentially achieving privilege escalation by manipulating query execution.

MitigationUpgrade the Amazon Redshift Python Connector to version 2.1.5 or revert to version 2.1.3 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
Redshift ConnectorApplication
Affected:= 2.1.4

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. Check installed connector version
    Run 'pip show amazon-redshift-connector' or 'pip list | grep -i redshift' to retrieve the installed version of the Amazon Redshift Python Connector
    Affected if Version is exactly 2.1.4
  2. Identify usage of get_schemas API
    Search project codebase for occurrences of 'get_schemas' method calls, for example: grep -r 'get_schemas' . or use IDE find functionality across Python files
    Affected if The method is called in the codebase and accepts user-controlled input as the schema parameter
  3. Identify usage of get_tables API
    Search project codebase for occurrences of 'get_tables' method calls, for example: grep -r 'get_tables' . or use IDE find functionality across Python files
    Affected if The method is called in the codebase and accepts user-controlled input as the table parameter
  4. Identify usage of get_columns API
    Search project codebase for occurrences of 'get_columns' method calls, for example: grep -r 'get_columns' . or use IDE find functionality across Python files
    Affected if The method is called in the codebase and accepts user-controlled input as the column parameter
  5. Verify input sanitization on metadata API calls
    Review code paths where get_schemas, get_tables, or get_columns are invoked to determine if input parameters are derived from user request data without parameterized queries or input validation
    Affected if User input is passed directly to these metadata APIs without sanitization or use of parameterized queries

User is affected if the Amazon Redshift Python Connector version is exactly 2.1.4 AND any of the metadata APIs (get_schemas, get_tables, get_columns) are used with unsanitized user-supplied input.

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 Python Connector to version 2.1.5 or revert to version 2.1.3 to remediate the SQL injection vulnerability.

Recommended fix High confidence

2.1.5

  1. Check current installed version of amazon-redshift-python-connector by running: pip show amazon-redshift-python-connector
  2. Upgrade to the fixed version 2.1.5 using pip: pip install amazon-redshift-python-connector==2.1.5
  3. Verify the upgrade was successful by running: pip show amazon-redshift-python-connector and confirming the version is 2.1.5
  4. Test that the Metadata APIs (get_schemas, get_tables, get_columns) function correctly with your application

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

Fix this in Redshift Connector Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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