Advisory

GHSA-q6j3-c4wc-63vw

Also known as: None

Summary

CSRF tokens leaked in URL by canned query form

Details

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 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.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2020-08-11 14:54 UTC
Modified
2024-12-02 05:44 UTC

Affected packages and fixes

datasette

PyPI · All systems

Affected

  • introduced 0, fixed 0.46 (ecosystem)

Fixed versions

0.46

Fix

  • Fixed version 0.46
    pip install --upgrade datasette==0.46

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences