Amazon Redshift Python Connector vulnerable to SQL InjectionGHSA-8gc2-vq6m-rwjw
HIGHGHSA-8gc2-vq6m-rwjw is a high-severity (CVSS 8) SQL Injection vulnerability in redshift-connector. A fix is available for redshift-connector — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-8gc2-vq6m-rwjw.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
redshift-connectorReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
Description
Summary
A SQL injection in the Amazon Redshift Python Connector in version 2.1.4 allows a user to gain escalated privileges via schema injection in the get_schemas, get_tables, or get_columns Metadata APIs. Users should upgrade to the driver version 2.1.5 or revert to driver version 2.1.3.
Impact
A SQL injection is possible in the Amazon Redshift Python Connector, version 2.1.4, when leveraging metadata APIs to retrieve information about database schemas, tables, or columns.
Impacted versions: Amazon Redshift Python Connector version 2.1.4.
Patches
The issue described above has been addressed in the Amazon Redshift Python Connector, version 2.1.5.
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 Python Connector, version 2.1.3.
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | redshift-connector | ≥ 2.1.4&&< 2.1.5 | 2.1.5pip install --upgrade 'redshift-connector==2.1.5' |
Affected Products
redshift connectoramazonDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for redshift-connector, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update redshift-connector to 2.1.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-8gc2-vq6m-rwjw is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.
Frequently Asked Questions
Is GHSA-8gc2-vq6m-rwjw in your dependencies?
Find it across PyPI, including transitive dependencies.