Open Redirect in flask-appbuilder (CVE-2021-32805)
Summary
Vulnerability in flask-appbuilder (CVE-2021-32805). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 3.3.2 or later.
Original description
The description as published by the source.
Flask-AppBuilder is an application development framework, built on top of Flask. In affected versions if using Flask-AppBuilder OAuth, an attacker can share a carefully crafted URL with a trusted domain for an application built with Flask-AppBuilder, this URL can redirect a user to a malicious site. This is an open redirect vulnerability. To resolve this issue upgrade to Flask-AppBuilder 3.2.2 or above. If upgrading is infeasible users may filter HTTP traffic containing ?next={next-site} where the next-site domain is different from the application you are protecting as a workaround.
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2021-32805 has been found in flask-appbuilder.
Risk of unauthorized operations or information disclosure.
What to do: upgrade flask-appbuilder to 3.3.2 or later.
If unsure, ask your IT team or search "flask-appbuilder CVE-2021-32805" on the vendor's site.
CVE-2021-32805 (flask-appbuilder) — CWE-601
Attack vector: remote (network-reachable) / unauthenticated
Patched: 3.3.2 — 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.
A vulnerability (CWE-601) exists in flask-appbuilder.
Check the vendor advisory for the affected versions of flask-appbuilder.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 3.3.2.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'flask-appbuilder' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'flask-appbuilder' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
flask-appbuilderを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade flask-appbuilder to 3.3.2ステージング環境で 3.3.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- web github.com
- web github.com
- web pypi.org