Issue

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.

Patches

Version 3.4.5 and soon to be released 4.0.0 are patched.

Workarounds

If you aren't using authentication tokens - you can set the SECURITY_TOKEN_MAX_AGE to "0" (seconds) which should make the token unusable.

References

None

References

• GHSA-hh7m-rx4f-4vpv
• Flask-Middleware/flask-security#422
• Flask-Middleware/flask-security@61d3131
• Flask-Middleware/flask-security@6d50ee9
• https://github.com/Flask-Middleware/flask-security/releases/tag/3.4.5
• https://pypi.org/project/Flask-Security-Too
• https://nvd.nist.gov/vuln/detail/CVE-2021-21241