CSRF can expose users authentication token

高 7.4CVE-2021-21241 · GHSA-hh7m-rx4f-4vpv · PYSEC-2021-91 · 11/01/2021 公開 · 17/06/2026 更新

要点

CVE-2021-21241 は flask-security-too, flask-security-too (flask-security-too project) に影響する深刻度「高」 (CVSS 7.4) の脆弱性です。
今後30日間に悪用される確率（EPSS）：0.93%（全脆弱性の 60.7% より高い）。
対処：3.4.5 以降に更新してください。

パッケージ	影響を受けるバージョン	修正済みバージョン
flask-security-too PyPI	`≥ 3.3.0, < 3.4.5`	`3.4.5`
flask-security-too flask-security-too_project	`≥ 3.3.0, < 3.4.5`	`3.4.5`

概要

Issue

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.

Patches

Version 3.4.5 and soon to be released 4.0.0 are patched.

Workarounds

If you aren't using authentication tokens - you can set the SECURITY_TOKEN_MAX_AGE to "0" (seconds) which should make the token unusable.

References

None

NVD の説明

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.