VYPR
← All advisories
High severityNVD Advisory· Published Jan 11, 2021· Updated Aug 3, 2024

CSRF can expose users authentication token in Flask-Security-Too

CVE-2021-21241

Description

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.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
Flask-Security-TooPyPI
>= 3.3.0, < 3.4.53.4.5

Affected products

16

Patches

Vulnerability mechanics

References

14

News mentions

0

No linked articles in our index yet.