Flask Security Too
Approved changes feed: RSS · Atom
cpe:2.3:a:flask-middleware:flask-security-too:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Flask Middleware (5edf2960-d2bd-5e4d-82b8-232e23ac3e28) |
|---|---|
| Product | Flask Security Too (3b7cae13-3208-5e0a-a518-e95fd67d977e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2021-21241 |
vulnerable | 2026-06-08 05:29:11.450156 |
CSRF can expose users authentication token in Flask-Security-Too
HIGH (7.4)
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.
Published: 2021-01-11T20:35:16.000Z
Updated: 2024-08-03T18:09:15.009Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.