PYSEC-2021-91

See a problem?
Import Source
https://github.com/pypa/advisory-database/blob/main/vulns/flask-security-too/PYSEC-2021-91.yaml
JSON Data
https://api.osv.dev/v1/vulns/PYSEC-2021-91
Aliases
Published
2021-01-11T21:15:00Z
Modified
2023-11-08T04:04:39.251638Z
Summary
[none]
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 SECURITYTOKENMAX_AGE to "0" (seconds) which should make the token unusable.

References

Affected packages

PyPI / flask-security-too

Package

Name
flask-security-too
View open source insights on deps.dev
Purl
pkg:pypi/flask-security-too

Affected ranges

Type
GIT
Repo
https://github.com/Flask-Middleware/flask-security
Events
Introduced
0 Unknown introduced commit / All previous commits are affected
Fixed
Fixed
Type
ECOSYSTEM
Events
Introduced
3.3.0
Fixed
3.4.5

Affected versions

3.*

3.3.0
3.3.1
3.3.2
3.3.3
3.4.0
3.4.1
3.4.2
3.4.3
3.4.4