SQL Injection in the Amazon Redshift JDBC Driver affecting v2.1.0.31 - How can we verify that we have updated the JDBC Driver in all the affected places?

Question

Regarding this update:
Published: 2024-12-24
Updated: 2024-12-26
Title: SQL Injection in the Amazon Redshift JDBC Driver affecting v2.1.0.31

Description
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.

How can we verify that we have updated the JDBC Driver in all the affected places?

Anand Malayil Sasi · Answer

Hi,
You can use database auditing with the help of Amazon Redshift logs to gather information about clients connecting to your cluster. Hopefully this will help you to identify them and make the necessary updates to the driver.
Please refer the documentation below for details.

https://docs.aws.amazon.com/redshift/latest/mgmt/db-auditing.html

SQL Injection in the Amazon Redshift JDBC Driver affecting v2.1.0.31 - How can we verify that we have updated the JDBC Driver in all the affected places?

Add your answer

Relevant content