Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| pallets-eco | Flask-Security-Too | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Pallets-eco | Flask-security-too |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-97r5-pg8x-p63p | Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.352% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pallets-eco
Pallets-eco flask-security-too |
|
| Vendors & Products |
Pallets-eco
Pallets-eco flask-security-too |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Flask-Security-Too allows users to add security features to their Flask applicationa. Version 5.8.0's OAuth reauthentication flow can mark a session as fresh after verifying an OAuth account that belongs to a different user. If an attacker can operate an already-authenticated but stale victim session, they can complete OAuth verification using their own OAuth identity. The victim session is then treated as recently reauthenticated, allowing freshness-protected account actions to proceed. Version 5.8.1 contains a fix for this issue. | |
| Title | Flask-Security-Too OAuth reauthentication freshness bypass via cross- user OAuth identity acceptance | |
| Weaknesses | CWE-287 | |
| References |
| |
| Metrics |
cvssV4_0
|