GHSA-fxq4-r6mr-9x64
GHSA-fxq4-r6mr-9x64 · CSRF Vuln can expose user's QRcode
This page contains facts from public vulnerability sources. Check the original advisory before updating.
### 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
Fix available
- Published
- Updated
Stack: python
Affected products and versions
flask-security-too PyPI
- Versions
- 3.2.0
- 3.3.0
- 3.3.0rc1
- 3.3.0rc2
- 3.3.0rc3
- 3.3.1
- 3.3.2
- 3.3.3
- 3.4.0
- 3.4.1
- 3.4.2
- 3.4.3
- 3.4.4
- Affected ranges
- ECOSYSTEM: ≥ 3.2.0, < 3.4.5
Update to 3.4.5