aws amazon-redshift-jdbc-driver up to 2.1.0.27 sql injection

Summaryinfo

A vulnerability labeled as critical has been found in aws amazon-redshift-jdbc-driver up to 2.1.0.27. This issue affects some unknown processing. Executing a manipulation can lead to sql injection. This vulnerability is registered as CVE-2024-32888. It is possible to launch the attack remotely. No exploit is available. The affected component should be upgraded.

Detailsinfo

A vulnerability was found in aws amazon-redshift-jdbc-driver up to 2.1.0.27. It has been declared as critical. This vulnerability affects an unknown part. The manipulation with an unknown input leads to a sql injection vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

The Amazon JDBC Driver for Redshift is a Type 4 JDBC driver that provides database connectivity through the standard JDBC application program interfaces (APIs) available in the Java Platform, Enterprise Editions. Prior to version 2.1.0.28, SQL injection is possible when using the non-default connection property `preferQueryMode=simple` in combination with application code which has a vulnerable SQL that negates a parameter value. There is no vulnerability in the driver when using the default, extended query mode. Note that `preferQueryMode` is not a supported parameter in Redshift JDBC driver, and is inherited code from Postgres JDBC driver. Users who do not override default settings to utilize this unsupported query mode are not affected. This issue is patched in driver version 2.1.0.28. As a workaround, do not use the connection property `preferQueryMode=simple`. (NOTE: Those who do not explicitly specify a query mode use the default of extended query mode and are not affected by this issue.)

The advisory is shared for download at github.com. This vulnerability was named CVE-2024-32888 since 04/19/2024. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1505.

Upgrading to version 2.1.0.28 eliminates this vulnerability. Applying the patch 0d354a5f26ca23f7cac4e800e3b8734220230319 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-1847). VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Type

• Hardware Driver Software

Vendor

• aws

Name

• amazon-redshift-jdbc-driver

Version

• 2.1.0.0
• 2.1.0.1
• 2.1.0.2
• 2.1.0.3
• 2.1.0.4
• 2.1.0.5
• 2.1.0.6
• 2.1.0.7
• 2.1.0.8
• 2.1.0.9
• 2.1.0.10
• 2.1.0.11
• 2.1.0.12
• 2.1.0.13
• 2.1.0.14
• 2.1.0.15
• 2.1.0.16
• 2.1.0.17
• 2.1.0.18
• 2.1.0.19
• 2.1.0.20
• 2.1.0.21
• 2.1.0.22
• 2.1.0.23
• 2.1.0.24
• 2.1.0.25
• 2.1.0.26
• 2.1.0.27

License

• open-source

Website

• Product: https://github.com/aws/amazon-redshift-jdbc-driver/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion