CVE-2021-21241 HIGH

CVE-2021-21241: CSRF can expose users authentication token in Flask-Security-Too

Vendor Flask-Middleware
Product flask-security-too
Weakness CWE-352 · CSRF
Published January 11, 2021
Last update August 3, 2024

CVSS base score

7.4/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction Required
Confidentiality High
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

What the vulnerability does

01Description

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.

Key dates

02Disclosure timeline

January 11, 2021 CVE published
August 3, 2024 Record updated

Related vulnerabilities

04Related CVE