← Back
CVE-2024-6221
Vulnerability in flask-cors (CVE-2024-6221)
Summary
vulnerability in flask-cors (CVE-2024-6221). Confidential information can be exposed externally. Mitigation: upgrade to `4.0.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-6221** has been found in flask-cors.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade flask-cors to **4.0.2** or later.
If unsure, ask your IT team or search "flask-cors CVE-2024-6221" on the vendor's site.
CVE-2024-6221 (flask-cors) — CWE-284 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: `4.0.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.
❓ What is the problem
**A vulnerability** (CWE-284) exists in flask-cors.
📍 Affected scope
flask-cors — .
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **4.0.2**.
🛡️ 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-cors' .` 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-cors' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `flask-cors` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade flask-cors to 4.0.2ステージング環境で 4.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
flask-cors
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.2"}]}]
pip
Flask-Cors
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"4.0.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-6221
- advisory https://github.com/advisories/GHSA-hxwh-jpp2-84pm
- package https://github.com/corydolphin/flask-cors
- web https://github.com/corydolphin/flask-cors/commit/03aa3f8e2256437f7bad96422a747b98ab5e31bf
- web https://huntr.com/bounties/a42935fc-6f57-4818-bca4-3d528235df4d
- web https://github.com/corydolphin/flask-cors/issues/362
- web https://github.com/corydolphin/flask-cors/pull/363
- web https://github.com/corydolphin/flask-cors/pull/368
- web https://github.com/corydolphin/flask-cors/commit/7ae310c56ac30e0b94fb42129aa377bf633256ec
- web https://github.com/corydolphin/flask-cors/commit/c8514760cf03fcce16d77f6db7007aad429c4548
- web https://github.com/corydolphin/flask-cors/releases
- web https://github.com/pypa/advisory-database/tree/main/vulns/flask-cors/PYSEC-2024-71.yaml
- web https://github.com/pypa/advisory-database/tree/main/vulns/flask-cors/PYSEC-2024-260.yaml