datasette@0.45a3 vulnerabilities

An open source multi-tool for exploring and publishing data

  • latest version

    0.65.1

  • latest non vulnerable version

  • first published

    7 years ago

  • latest version published

    1 months ago

  • licenses detected

  • Direct Vulnerabilities

    Known vulnerabilities in the datasette package. This does not include vulnerabilities belonging to this package’s dependencies.

    How to fix?

    Automatically find and fix vulnerabilities affecting your projects. Snyk scans for vulnerabilities and provides fixes for free.

    Fix for free
    VulnerabilityVulnerable Version
    • M
    Cross-site Scripting (XSS)

    datasette is an An open source multi-tool for exploring and publishing data

    Affected versions of this package are vulnerable to Cross-site Scripting (XSS). There was a security hole with the ?_trace=1 feature as it did not correctly escape generated HTML.

    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.

    How to fix Cross-site Scripting (XSS)?

    Upgrade datasette to version 0.56.1 or higher.

    [,0.56.1)
    • M
    Cross-site Scripting (XSS)

    datasette is an An open source multi-tool for exploring and publishing data

    Affected versions of this package are vulnerable to Cross-site Scripting (XSS) via the ?_trace= debugging feature which does not correctly escape generated HTML.

    How to fix Cross-site Scripting (XSS)?

    Upgrade datasette to version 0.56.1, 0.57 or higher.

    [0,0.56.1)[0.57a0,0.57)
    • M
    Information Exposure

    datasette is an An open source multi-tool for exploring and publishing data

    Affected versions of this package are vulnerable to Information Exposure. The HTML form for a read-only canned query includes the hidden CSRF token field for writable canned queries. Submitting those read-only forms exposes the CSRF token in the URL - for example: 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.

    How to fix Information Exposure?

    Upgrade datasette to version 0.46 or higher.

    [,0.46)