← Back
CVE-2024-12745
SQL Injection in redshift-connector (CVE-2024-12745)
Summary
SQL injection in redshift-connector (CVE-2024-12745). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `2.1.5` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-12745** has been found in redshift-connector.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade redshift-connector to **2.1.5** or later.
If unsure, ask your IT team or search "redshift-connector CVE-2024-12745" on the vendor's site.
CVE-2024-12745 (redshift-connector) — CWE-89 /
Attack vector: remote (network-reachable)
Patched: `2.1.5` — apply immediately
Workaround: Use the previous version of the Amazon Redshift Python Connector, version 2.1.3.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**SQL injection** (CWE-89) exists in redshift-connector.
📍 Affected scope
redshift-connector — .
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **2.1.5**.
🛡️ Workaround
Workaround: Use the previous version of the Amazon Redshift Python Connector, version 2.1.3.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'redshift-connector' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'redshift-connector' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `redshift-connector` を grep し、稼働しているサービス・バージョンを把握する。
-
5Apply temporary workaround mitigate
Use the previous version of the Amazon Redshift Python Connector, version 2.1.3.パッチが適用されるまでの応急処置として、Use the previous version of the Amazon Redshift Python Connector, version 2.1.3. を実施。回避策の副作用 (機能低下) を確認した上で。
-
6Apply patch patch
Upgrade redshift-connector to 2.1.5ステージング環境で 2.1.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
redshift-connector
[{"type":"ECOSYSTEM","events":[{"introduced":"2.1.4"},{"fixed":"2.1.5"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-12745
- advisory https://github.com/advisories/GHSA-8gc2-vq6m-rwjw
- package https://github.com/aws/amazon-redshift-python-driver
- package https://pypi.org/project/redshift-connector
- web https://github.com/aws/amazon-redshift-python-driver/security/advisories/GHSA-8gc2-vq6m-rwjw
- web https://aws.amazon.com/security/security-bulletins/AWS-2024-015
- web https://github.com/aws/amazon-redshift-python-driver/releases/tag/v2.1.5