Skip to content

SQL Injection in the Amazon Redshift ODBC Driver affecting v2.1.5.0

High
zurowskik published GHSA-g63m-5vjv-wr3v Dec 24, 2024

Package

AmazonRedshiftODBC (Amazon)

Affected versions

2.1.5.0

Patched versions

2.1.6.0

Description

Summary

A SQL injection in the Amazon Redshift ODBC Driver in version 2.1.5.0 (Windows or Linux) allows a user to gain escalated privileges via schema injection in the SQLTables or SQLColumns Metadata APIs. Users are recommended to upgrade to the driver version 2.1.6.0 or revert to version 2.1.4.0.

Impact

A SQL injection is possible in the Amazon Redshift ODBC Driver, version 2.1.5.0 (Windows or Linux), when leveraging metadata APIs to retrieve information about database schemas, tables, or columns.

Impacted versions: Amazon Redshift ODBC Driver version 2.1.5.0.

Patches

The issue described above has been addressed in the Amazon Redshift ODBC Driver, version 2.1.6.0.

The patch implemented in this version ensures that every metadata command input is sent to the Redshift server as part of a parameterized query, using either QUOTE_IDENT(string) or QUOTE_LITERAL(string). After processing all the inputs into quoted identifiers or literals, the metadata command is composed using these inputs and then executed on the server.

Workarounds

Use the previous version of the Amazon Redshift JDBC Driver, 2.1.4.0, for either Windows or Linux.

References

If you have any questions or comments about this advisory we ask that you contact AWS/Amazon Security via our vulnerability reporting page [1] or directly via email to [email protected]. Please do not create a public GitHub issue.

[1] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

CVE ID

CVE-2024-12746

Weaknesses

No CWEs

Credits