← Back
GHSA-f66q-9rf6-8795
Authentication Bypass in Flask-Security-Too (GHSA-f66q-9rf6-8795)
Summary
authentication bypass in Flask-Security-Too (GHSA-f66q-9rf6-8795). Risk of unauthorized operations or information disclosure. Exploitable via `POST /wan-verify`. Mitigation: upgrade to `5.8.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-f66q-9rf6-8795** has been found in Flask-Security-Too.
Attackers can target a specific entry point like `POST /wan-verify` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade Flask-Security-Too to **5.8.1** or later.
If unsure, ask your IT team or search "Flask-Security-Too GHSA-f66q-9rf6-8795" on the vendor's site.
GHSA-f66q-9rf6-8795 (Flask-Security-Too) — CWE-287 /
Attack surface: POST /wan-verify / POST /wan-verify/ / `main` / `oauth_glue.py`
Patched: `5.8.1` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**authentication bypass** (CWE-287) exists in Flask-Security-Too. Attackers reach the vulnerable code path via `POST /wan-verify` without authentication.
📍 Affected scope
Flask-Security-Too — . Attack surface: POST /wan-verify / POST /wan-verify/ / `main` / `oauth_glue.py`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **5.8.1**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual `POST /wan-verify` requests with malformed payloads or SQL meta-characters. Run `grep -r 'Flask-Security-Too' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'Flask-Security-Too' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `Flask-Security-Too` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /wan-verify' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /wan-verify` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade Flask-Security-Too to 5.8.1ステージング環境で 5.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /wan-verify on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
Flask-Security-Too
[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}]