← Back
CVE-2019-7164
SQL Injection in sqlalchemy (CVE-2019-7164)
Summary
SQL injection in sqlalchemy (CVE-2019-7164). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `1.3.0b3` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2019-7164** has been found in sqlalchemy.
Successful exploitation can lead to full system takeover. CVSS score: ?/10.
What to do: upgrade sqlalchemy to **1.3.0b3** or later.
If unsure, ask your IT team or search "sqlalchemy CVE-2019-7164" on the vendor's site.
CVE-2019-7164 (sqlalchemy) — CWE-89 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `1.3.0b3` — apply immediately
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 sqlalchemy.
📍 Affected scope
sqlalchemy — .
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **1.3.0b3**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'sqlalchemy' .` 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 'sqlalchemy' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `sqlalchemy` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade sqlalchemy to 1.3.0b3ステージング環境で 1.3.0b3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
sqlalchemy
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.3.0b3"}]}]
References
- advisory https://github.com/advisories/GHSA-887w-45rq-vxgf
- advisory https://nvd.nist.gov/vuln/detail/CVE-2019-7164
- package https://github.com/sqlalchemy/sqlalchemy
- web https://github.com/sqlalchemy/sqlalchemy/issues/4481
- web https://lists.debian.org/debian-lts-announce/2019/03/msg00020.html
- web https://access.redhat.com/errata/RHSA-2019:0984
- web https://access.redhat.com/errata/RHSA-2019:0981
- web http://lists.opensuse.org/opensuse-security-announce/2019-08/msg00087.html
- web http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00010.html
- web http://lists.opensuse.org/opensuse-security-announce/2019-09/msg00016.html
- web https://www.oracle.com/security-alerts/cpujan2021.html
- web https://github.com/sqlalchemy/sqlalchemy/commit/30307c4616ad67c01ddae2e1e8e34fabf6028414
- web https://github.com/pypa/advisory-database/tree/main/vulns/sqlalchemy/PYSEC-2019-123.yaml
- web https://lists.debian.org/debian-lts-announce/2021/11/msg00005.html