Amazon Redshift JDBC Driver 2.1.0.31 Metadata API getSchemas/getTables/getColumns sql injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.6 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Amazon Redshift JDBC Driver 2.1.0.31. This impacts the function getSchemas/getTables/getColumns of the component Metadata API. The manipulation leads to sql injection.
This vulnerability is referenced as CVE-2024-12744. Remote exploitation of the attack is possible. No exploit is available.
It is suggested to upgrade the affected component.
Details
A vulnerability was found in Amazon Redshift JDBC Driver 2.1.0.31 and classified as critical. This issue affects the function getSchemas/getTables/getColumns of the component Metadata API. The manipulation with an unknown input leads to a sql injection vulnerability. Using CWE to declare the problem leads to CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-12744 since 12/18/2024. The exploitation is known to be easy. The attack may be initiated remotely. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The vulnerability scanner Nessus provides a plugin with the ID 214311 (RedShift JDBC Driver < 2.1.0.32 (CVE-2024-12744)), which helps to determine the existence of the flaw in a target environment.
Upgrading to version 2.1.0.32 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at Tenable (214311). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 5.5
VulDB Temp Score: 5.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 8.0
CNA Vector (AMZN): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 214311
Nessus Name: RedShift JDBC Driver < 2.1.0.32 (CVE-2024-12744)
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Redshift JDBC Driver 2.1.0.32
Timeline
12/18/2024 🔍12/24/2024 🔍
12/24/2024 🔍
09/19/2025 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2024-12744 (🔍)
GCVE (CVE): GCVE-0-2024-12744
GCVE (VulDB): GCVE-100-289265
Entry
Created: 12/24/2024 17:59Updated: 09/19/2025 16:13
Changes: 12/24/2024 17:59 (78), 01/18/2025 00:44 (2), 09/19/2025 16:13 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.