CVEs-PoC/2021/CVE-2021-21241.md

### [CVE-2021-21241](https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-21241)
![](https://img.shields.io/static/v1?label=Product&message=flask-security-too&color=blue)
![](https://img.shields.io/static/v1?label=Version&message=%3E%3D%203.3.0%2C%20%3C%203.4.5%20&color=brightgreen)
![](https://img.shields.io/static/v1?label=Vulnerability&message=CWE-352%3A%20Cross-Site%20Request%20Forgery%20(CSRF)&color=brightgreen)

### 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.

### POC

#### Reference
- https://github.com/Flask-Middleware/flask-security/commit/61d313150b5f620d0b800896c4f2199005e84b1f

#### Github
No PoCs found on GitHub currently.