← Back
GHSA-w2j7-f3c6-g8cw
Open Redirect in Flask-Security (GHSA-w2j7-f3c6-g8cw)
Summary
vulnerability in Flask-Security (GHSA-w2j7-f3c6-g8cw). Risk of unauthorized operations or information disclosure. Exploitable via ``whitelist.com``. Mitigation: upgrade to `5.8.1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **GHSA-w2j7-f3c6-g8cw** has been found in Flask-Security.
Attackers can target a specific entry point like ``whitelist.com`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade Flask-Security to **5.8.1** or later.
If unsure, ask your IT team or search "Flask-Security GHSA-w2j7-f3c6-g8cw" on the vendor's site.
GHSA-w2j7-f3c6-g8cw (Flask-Security) — CWE-601 /
Attack surface: `whitelist.com`
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
**A vulnerability** (CWE-601) exists in Flask-Security. Attackers reach the vulnerable code path via ``whitelist.com`` without authentication.
📍 Affected scope
Flask-Security — . Attack surface: `whitelist.com`.
🔥 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 request patterns matching this CVE's known IOCs. Run `grep -r 'Flask-Security' .` 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' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `Flask-Security` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade Flask-Security to 5.8.1ステージング環境で 5.8.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
pip
Flask-Security
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.8.1"}]}]
References
- web https://github.com/pallets-eco/flask-security/security/advisories/GHSA-w2j7-f3c6-g8cw
- web https://nvd.nist.gov/vuln/detail/CVE-2023-49438
- web https://advisories.gitlab.com/pypi/flask-security-too/CVE-2023-49438
- web https://osv.dev/vulnerability/CVE-2023-49438
- web https://github.com/advisories/GHSA-w2j7-f3c6-g8cw