Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2024-12746: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in Amazon Amazon Redshift ODBC Driver

0
High
VulnerabilityCVE-2024-12746cvecve-2024-12746cwe-89
Published: Tue Dec 24 2024 (12/24/2024, 16:16:37 UTC)
Source: CVE Database V5
Vendor/Project: Amazon
Product: Amazon Redshift ODBC Driver

Description

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.

AI-Powered Analysis

AILast updated: 10/14/2025, 19:01:28 UTC

Technical Analysis

CVE-2024-12746 is a SQL injection vulnerability classified under CWE-89 found in the Amazon Redshift ODBC Driver version 2.1.5.0 for Windows and Linux. The vulnerability arises from improper neutralization of special elements in SQL commands within the SQLTables and SQLColumns Metadata APIs. This flaw allows an attacker with limited privileges to inject malicious SQL code, thereby escalating their privileges within the Redshift environment. The vulnerability does not require authentication or user interaction, making it remotely exploitable over the network. The CVSS 4.0 vector indicates network attack vector (AV:N), low attack complexity (AC:L), no privileges required (PR:L), and no user interaction (UI:P), with high impact on confidentiality, integrity, and availability. The vulnerability affects metadata retrieval functions, which are commonly used by applications and administrators to query database schema information. Exploiting this vulnerability could allow attackers to execute arbitrary SQL commands, potentially leading to unauthorized data access, modification, or disruption of database services. Amazon has addressed this issue in driver version 2.1.6.0 and recommends upgrading or alternatively reverting to the prior stable version 2.1.4.0. No public exploits have been reported yet, but the high severity and ease of exploitation make timely remediation essential.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the confidentiality, integrity, and availability of data stored in Amazon Redshift clusters accessed via the affected ODBC driver. Attackers exploiting this flaw could escalate privileges and gain unauthorized access to sensitive business intelligence data, customer information, or intellectual property. This could lead to data breaches, regulatory non-compliance (e.g., GDPR violations), financial losses, and reputational damage. Organizations relying on Redshift for critical analytics, especially in regulated industries such as finance, healthcare, and government, face heightened risk. Additionally, disruption of database services due to malicious SQL commands could impact operational continuity. Since the vulnerability affects a widely used data access driver, the attack surface includes any system or user connecting to Redshift via the vulnerable ODBC driver, increasing the scope of potential impact across European enterprises using AWS analytics services.

Mitigation Recommendations

European organizations should immediately verify their use of Amazon Redshift ODBC Driver version 2.1.5.0 and take prompt action. The primary mitigation is to upgrade the driver to version 2.1.6.0, which contains the security fix. If immediate upgrade is not feasible, reverting to version 2.1.4.0 is a temporary workaround. Organizations should audit and restrict access to Redshift metadata APIs to trusted users only and monitor database logs for unusual metadata queries indicative of exploitation attempts. Implement network segmentation and strict access controls to limit exposure of Redshift endpoints. Employ runtime application self-protection (RASP) or database activity monitoring (DAM) solutions to detect and block SQL injection attempts. Regularly review and update incident response plans to include scenarios involving privilege escalation via SQL injection. Finally, ensure all relevant personnel are informed about the vulnerability and remediation steps to prevent delayed patching.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
AMZN
Date Reserved
2024-12-18T01:43:56.475Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 68ee9df131414aa8fc5b888f

Added to database: 10/14/2025, 7:01:05 PM

Last enriched: 10/14/2025, 7:01:28 PM

Last updated: 10/15/2025, 4:31:22 PM

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats