CVE-2021-21241
7.4 · HIGHOverview
CVE-2021-21241 is a high-severity vulnerability affecting flask-security-too_project flask-security-too. It was published on January 11, 2021 and has a CVSS 3.1 base score of 7.4 (HIGH).
This vulnerability has a CVSS 3.1 base score of 7.4, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
Technical 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.
Remediation
Check the references section for vendor advisories and patches from flask-security-too_project. Update flask-security-too to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|---|---|---|
| flask-security-too_project | flask-security-too | >= 3.3.0, < 3.4.5 | Affected |
References
Frequently Asked Questions
What is CVE-2021-21241?
CVE-2021-21241 is a high-severity vulnerability affecting flask-security-too_project flask-security-too. It was published on January 11, 2021 and has a CVSS 3.1 base score of 7.4 (HIGH).
How severe is CVE-2021-21241?
This vulnerability has a CVSS 3.1 base score of 7.4, rated HIGH. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.
How do I fix or remediate CVE-2021-21241?
Check the references section for vendor advisories and patches from flask-security-too_project. Update flask-security-too to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2021-21241?
CyberStrike's AI-powered security agents can automatically detect CVE-2021-21241 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.
Related HIGH CVEs from 2021
View all →systeminformation is an open source system and OS information library for node.js. A command injecti
An Improper Access Control Privilege Escalation Vulnerability was discovered in the User Setting of
An SQL injection Privilege Escalation Vulnerability was discovered in the Orion Platform reported by
Insecure deserialization leading to Remote Code Execution was detected in the Orion Platform version
Insecure Deserialization of untrusted data remote code execution vulnerability was discovered in Pat
Deserialization of Untrusted Data in the Web Console Chart Endpoint can lead to remote code executio
Insecure Deseralization of untrusted data remote code execution vulnerability was discovered in Patc
SAP Web Dispatcher versions - 7.49, 7.53, 7.77, 7.81, KRNL64NUC - 7.22, 7.22EXT, 7.49, KRNL64UC -7.2
uploader.php in the KCFinder integration project through 2018-06-01 for Drupal mishandles validation
An issue was discovered in the PageLayer plugin before 1.1.2 for WordPress. The pagelayer_settings_p
MK-AUTH through 19.01 K4.9 allows CSRF for password changes via the central/executar_central.php?aca
IBM Cloud Pak System 2.3 is vulnerable to cross-site request forgery which could allow an attacker t