Authenticated token exposure via unprotected GET
Published Jan 11, 2021 · Updated Aug 3, 2024
Cross-site request forgery in Flask-Security-Too 3.3.0 through 3.4.4 allows remote attackers to obtain an authenticated user's token via GET requests. Handlers for the /login and /change endpoints return the authenticated user's authentication token even though GET requests carry no CSRF protection. A victim must be authenticated and induced to visit a malicious third-party site; the exposed token can enable account access according to its configured lifetime.
Summary
What happened
Cross-site request forgery in Flask-Security-Too 3.3.0 through 3.4.4 allows remote attackers to obtain an authenticated user's token via GET requests. Handlers for the /login and /change endpoints return the authenticated user's authentication token even though GET requests carry no CSRF protection. A victim must be authenticated and induced to visit a malicious third-party site; the exposed token can enable account access according to its configured lifetime.
The record
- CVE
- CVE-2021-21241
- Published
- Jan 11, 2021
- Updated
- Aug 3, 2024
- Vendor
- Flask-Middleware
- Product
- Flask-Security-Too
- Classifications
- CWE-352, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 11, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 3.3.0, < 3.4.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo