Vulnerability in sqlparse (CVE-2021-32839)
Summary
Vulnerability in sqlparse (CVE-2021-32839). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.4.2 or later.
Original description
The description as published by the source.
sqlparse is a non-validating SQL parser module for Python. In sqlparse versions 0.4.0 and 0.4.1 there is a regular Expression Denial of Service in sqlparse vulnerability. The regular expression may cause exponential backtracking on strings containing many repetitions of '\r\n' in SQL comments. Only the formatting feature that removes comments from SQL statements is affected by this regular expression. As a workaround don't use the sqlformat.format function with keyword strip_comments=True or the --strip-comments command line flag when using the sqlformat command line tool. The issues has been fixed in sqlparse 0.4.2.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-32839 has been found in sqlparse.
Risk of unauthorized operations or information disclosure.
What to do: upgrade sqlparse to 0.4.2 or later.
If unsure, ask your IT team or search "sqlparse CVE-2021-32839" on the vendor's site.
CVE-2021-32839 (sqlparse) — CWE-400
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.4.2 — 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.
A vulnerability (CWE-400) exists in sqlparse.
Check the vendor advisory for the affected versions of sqlparse.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.4.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'sqlparse' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'sqlparse' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
sqlparseを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade sqlparse to 0.4.2ステージング環境で 0.4.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Debian DEBIAN-CVE-2021-32839 sqlparse Fixed in: 0.4.2-1
References
- advisory github.com
- advisory nvd.nist.gov
- advisory securitylab.github.com
- package github.com
- patch github.com
- web github.com
- web lists.debian.org