Advisory

PYSEC-2021-91

Also known as: CVE-2021-21241, GHSA-hh7m-rx4f-4vpv

Summary

The record has no summary.

Details

The Python "Flask-Security-Too" package is used for adding security features to your Flask application. It is an is a independently maintained version of Flask-Security based on the 3.0.0 version of Flask-Security. In Flask-Security-Too from version 3.3.0 and before version 3.4.5, the /login and /change endpoints can return the authenticated user's authentication token in response to a GET request. Since GET requests aren't protected with a CSRF token, this could lead to a malicious 3rd party site acquiring the authentication token. Version 3.4.5 and version 4.0.0 are patched. As a workaround, if you aren't using authentication tokens - you can set the SECURITY_TOKEN_MAX_AGE to "0" (seconds) which should make the token unusable.

Severity

Not rated by the source.

Dates

Published
2021-01-11 21:15 UTC
Modified
2023-11-08 04:04 UTC

Affected packages and fixes

flask-security-too

PyPI · All systems

Affected

  • introduced 3.3.0, fixed 3.4.5 (ecosystem)

Fixed versions

3.4.5

Fix

  • Fixed version 3.4.5
    pip install --upgrade flask-security-too==3.4.5

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: PyPA Advisory Database · CC BY 4.0

Sources & licences