Authentication Bypass in flask-appbuilder (CVE-2021-41265)
Summary
Authentication bypass in flask-appbuilder (CVE-2021-41265). Confidential information can be exposed externally. Mitigation: upgrade to 3.3.4 or later.
Original description
The description as published by the source.
Impact
Improper authentication on the REST API. Allows for a malicious actor with a carefully crafted request to successfully authenticate and gain access to existing protected REST API endpoints. Only affects non database authentication types, and new REST API endpoints.
Patches
Upgrade to Flask-AppBuilder 3.3.4
For more information
If you have any questions or comments about this advisory:
- Open an issue in https://github.com/dpgaspar/Flask-AppBuilder
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-41265 has been found in flask-appbuilder.
Confidential information can be exposed externally.
What to do: upgrade flask-appbuilder to 3.3.4 or later.
If unsure, ask your IT team or search "flask-appbuilder CVE-2021-41265" on the vendor's site.
CVE-2021-41265 (flask-appbuilder) — CWE-287
Attack vector: remote (network-reachable) / no user interaction
Patched: 3.3.4 — 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.
Authentication bypass (CWE-287) exists in flask-appbuilder.
Check the vendor advisory for the affected versions of flask-appbuilder.
Severity: ?. Confidential information can be exposed externally.
Update to 3.3.4.
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.4ステージング環境で 3.3.4 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com