CSRF tokens leaked in URL by canned query form
Medium4.3Published Aug 11, 2020 · updated Dec 2, 2024
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| datasette PyPI | < 0.46 | 0.46 |
Details and references
### Impact The HTML form for a read-only canned query includes the hidden CSRF token field added in #798 for writable canned queries (#698). This means that submitting those read-only forms exposes the CSRF token in the URL - for example on https://latest.datasette.io/fixtures/neighborhood_search submitting the form took me to: https://latest.datasette.io/fixtures/neighborhood_search?text=down&csrftoken=CSRFTOKEN-HERE This token could potentially leak to an attacker if the resulting page has a link to an external site on it and the user clicks the link, since the token would be exposed in the referral logs. ### Patches A fix for this issue has been released in Datasette 0.46. ### Workarounds You can fix this issue in a Datasette instance without upgrading by copying the [0.46 query.html template](https://raw.githubusercontent.com/simonw/datasette/0.46/datasette/templates/query.html) into a custom `templates/` directory and running Datasette with the `--template-dir=templates/` option. ### References Issue 918 discusses this in details: https://github.com/simonw/datasette/issues/918 ### For more information Contact swillison at gmail with any questions.
- CVSS 3.1
- CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-200
More datasette advisories
All| Date | Advisory | Severity | Fixed in |
|---|---|---|---|
| Jun 72021 | Reflected cross-site scripting issue in Datasette CVE-2021-32670Medium7.2fixed in 0.56.1 | Medium7.2 | 0.56.1 |
| Aug 222023 | Datasette 1.0 alpha series leaks names of databases and tables to unauthenticated users CVE-2023-40570Medium5.3fixed in 1.0a4 | Medium5.3 | 1.0a4 |
| Nov 62025 | Open redirect endpoint in Datasette CVE-2025-64481Lowfixed in 0.65.2, 1.0a21 | Low | 0.65.2, 1.0a21 |