GHSA-fxq4-r6mr-9x64: Flask Security Too CSRF Vuln Can Expose User's Vulnerability

LOW
Share
CWE-352
Published
Advisory Summary

GHSA-fxq4-r6mr-9x64 is a LOW csrf vuln can expose user's vulnerability (CWE-352: Cross-Site Request Forgery (CSRF)) affecting Flask Security Too libraries in the PyPI ecosystem. The issue involves csrf vuln can expose user's qrcode. Remediation is available by upgrading affected packages to version 3.4.5.

GHSA-fxq4-r6mr-9x64 at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-fxq4-r6mr-9x64
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-352: Cross-Site Request Forgery (CSRF)
Affected Product Flask Security Too
Package Ecosystem PyPI
Published Date
Last Updated

How to Fix GHSA-fxq4-r6mr-9x64

To remediate this vulnerability, upgrade all affected Flask Security Too dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

Flask-Security-Too fixed: 3.4.5 
pip install Flask-Security-Too>=3.4.5
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release: 

pip show Flask-Security-Too

How to Check if You Are Affected

To determine whether your Python environment is affected by GHSA-fxq4-r6mr-9x64, inspect your installed packages using pip:

pip show Flask-Security-Too

Analyze the terminal output to locate any version of Flask Security Too in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.4.5), your application is affected.

Note: The pip show Flask-Security-Too command checks currently installed packages in your active Python environment.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-352: Cross-Site Request Forgery (CSRF), where the web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. In Flask Security Too, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact When a user is setting up two-factor authentication using an authenticator app, a QRcode is generated and made available via a GET request to /tf-qrcode. Since GETs do not have any CSRF protection, it is possible a malicious 3rd party could access the QRcode and therefore gain access to two-factor authentication codes. Note that the /tf-qrcode endpoint is ONLY accessible while the user is initially setting up their device. Once setup is complete, there is no vulnerability. ### Patches This is fixed in the upcoming 4.0.0 release. ### Workarounds You can provide your own URL for fetching the QRcode by defining SECURITY_TWO_FACTOR_QRCODE_URL and providing your own implementation (that presumably required a POST with CSRF protection). This would require changing the two-factor setup template as well. ### References None. ### For more information If you have any questions or comments about this advisory: * Read this pull request: #423

GHSA-fxq4-r6mr-9x64 Affected Flask Security Too Versions

1 component(s)
Fixed Versions:
3.4.5
Product / Package Ecosystem Affected Versions Fixed Version
Flask-Security-Too
pypi/Flask-Security-Too
PyPI
≥ 3.2.0
< 3.4.5
3.4.5

References

GitHub Advisory / Wiki ADVISORY
https://github.com/Flask-Middleware/flask-security/security/advisories/GHSA-fxq4-r6mr-9x64
Flask Security Too Security Information SECURITY
https://pypi.org/project/Flask-Security-Too

Frequently Asked Questions

What is GHSA-fxq4-r6mr-9x64?
GHSA-fxq4-r6mr-9x64 is a security vulnerability in Flask Security Too involving CSRF Vuln can expose user's QRcode under CWE-352: Cross-Site Request Forgery (CSRF).
Which Flask Security Too versions are affected?
Affected versions include releases prior to 3.4.5 across affected packages: Flask-Security-Too.
What version fixes GHSA-fxq4-r6mr-9x64?
Upgrading to 3.4.5 (or the latest patched release for your respective branch) resolves the vulnerability.
Is Flask-Security-Too affected?
Yes, Flask-Security-Too is affected in releases prior to 3.4.5. Upgrade your dependency to 3.4.5 or later.
What CWE is associated with GHSA-fxq4-r6mr-9x64?
GHSA-fxq4-r6mr-9x64 is classified under CWE-352: Cross-Site Request Forgery (CSRF) (The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.).
How can I check PyPI dependencies for GHSA-fxq4-r6mr-9x64?
Run the dependency tree command: 'pip show Flask-Security-Too'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
View Raw JSON 
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-fxq4-r6mr-9x64",
  "modified" : "2021-04-08T16:45:47Z",
  "published" : "2021-04-08T16:46:00Z",
  "aliases" : [ ],
  "summary" : "CSRF Vuln can expose user's QRcode",
  "details" : "### Impact\nWhen a user is setting up two-factor authentication using an authenticator app, a QRcode is generated and made available via a GET request to /tf-qrcode. Since GETs do not have any CSRF protection, it is possible a malicious 3rd party could access the QRcode and therefore gain access to two-factor authentication codes. Note that the /tf-qrcode endpoint is ONLY accessible while the user is initially setting up their device. Once setup is complete, there is no vulnerability.\n\n### Patches\nThis is fixed in the upcoming 4.0.0 release.\n\n### Workarounds\nYou can provide your own URL for fetching the QRcode by defining SECURITY_TWO_FACTOR_QRCODE_URL and providing your own implementation (that presumably required a POST with CSRF protection). This would require changing the two-factor setup template as well.\n\n### References\nNone.\n\n### For more information\nIf you have any questions or comments about this advisory:\n* Read this pull request: #423",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "PyPI",
      "name" : "Flask-Security-Too"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.2.0"
      }, {
        "fixed" : "3.4.5"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Flask-Middleware/flask-security/security/advisories/GHSA-fxq4-r6mr-9x64"
  }, {
    "type" : "WEB",
    "url" : "https://pypi.org/project/Flask-Security-Too"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-352" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2021-04-08T16:45:47Z",
    "nvd_published_at" : null
  }
}