Cross-Site Scripting (XSS) in datasette (CVE-2021-32670)
Summary
Cross-site scripting in datasette (CVE-2021-32670). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 0.56.1 or later.
Original description
The description as published by the source.
Impact
The ?_trace=1 debugging feature in Datasette does not correctly escape generated HTML, resulting in a reflected cross-site scripting vulnerability.
This vulnerability is particularly relevant if your Datasette installation includes authenticated features using plugins such as datasette-auth-passwords as an attacker could use the vulnerability to access protected data.
Patches
Datasette 0.57 and 0.56.1 both include patches for this issue.
Workarounds
If you run Datasette behind a proxy you can workaround this issue by rejecting any incoming requests with ?_trace= or &_trace= in their query string parameters.
References
For more information
If you have any questions or comments about this advisory:
- Open a discussion in simonw/datasette
- Email us at
swillison+datasette @ gmail.com
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-32670 has been found in datasette.
Risk of unauthorized operations or information disclosure.
What to do: upgrade datasette to 0.56.1 or later.
If unsure, ask your IT team or search "datasette CVE-2021-32670" on the vendor's site.
CVE-2021-32670 (datasette) — CWE-79
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 0.56.1 — apply immediately
Workaround: If you run Datasette behind a proxy you can workaround this issue by rejecting any incoming requests with ?_trace= or &_trace= in their query string parameters.
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.
Cross-site scripting (XSS) (CWE-79) exists in datasette.
Check the vendor advisory for the affected versions of datasette.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 0.56.1.
Workaround: If you run Datasette behind a proxy you can workaround this issue by rejecting any incoming requests with ?_trace= or &_trace= in their query string parameters.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'datasette' . 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 'datasette' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
datasetteを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
If you run Datasette behind a proxy you can workaround this issue by rejecting any incoming requests with `?_trace=` or `&_trace=` in their query string parameters.パッチが適用されるまでの応急処置として、If you run Datasette behind a proxy you can workaround this issue by rejecting any incoming requests with
?_trace=or&_trace=in their query string parameters. を実施。回避策の副作用 (機能低下) を確認した上で。 -
3Apply patch patch
Upgrade datasette to 0.56.1ステージング環境で 0.56.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- package github.com
- web github.com
- web github.com
- web datasette.io
- web github.com
- web owasp.org
- web pypi.org