製品・ソフトウェアに関する情報
Vulnerability Search
Python Flask-Security-Too パッケージにおけるクロスサイトリクエストフォージェリの脆弱性
Title Python Flask-Security-Too パッケージにおけるクロスサイトリクエストフォージェリの脆弱性
Summary

Python Flask-Security-Too パッケージには、クロスサイトリクエストフォージェリの脆弱性が存在します。

Possible impacts 情報を取得される可能性があります。
Solution

ベンダより正式な対策が公開されています。ベンダ情報を参照して適切な対策を実施してください。
Publication Date Jan. 2, 2021, midnight
Registration Date Sept. 22, 2021, 5:48 p.m.
Last Update Sept. 22, 2021, 5:48 p.m.
CVSS3.0 : 重要
Score 7.4
Vector CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
CVSS2.0 : 警告
Score 4.3
Vector AV:N/AC:M/Au:N/C:P/I:N/A:N
Affected System
Flask-Security-Too project
Flask-Security-Too 3.3.0 から 3.4.5 未満
CVE (情報セキュリティ 共通脆弱性識別子)
CWE (共通脆弱性タイプ一覧)
ベンダー情報
Change Log
No Changed Details Date of change
1 [2021年09月22日]
  掲載		 Sept. 22, 2021, 5:48 p.m.
NVD Vulnerability Information
CVE-2021-21241
Summary

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.

Publication Date Jan. 12, 2021, 6:15 a.m.
Registration Date Jan. 26, 2021, 10:40 a.m.
Last Update Nov. 21, 2024, 2:47 p.m.
Affected software configurations
Configuration1 or higher or less more than less than
cpe:2.3:a:flask-security-too_project:flask-security-too:*:*:*:*:*:*:*:* 3.3.0 3.4.5
Related information, measures and tools
Common Vulnerabilities List