← Back
CVE-2024-11042
Vulnerability in invokeai (CVE-2024-11042)
Summary
vulnerability in invokeai (CVE-2024-11042). Data can be tampered with by attackers. Exploitable via `POST /api/v1/images/delete`. Mitigation: upgrade to `5.3.0rc1` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-11042** has been found in invokeai.
Attackers can target a specific entry point like `POST /api/v1/images/delete` over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: ?/10.
What to do: upgrade invokeai to **5.3.0rc1** or later.
If unsure, ask your IT team or search "invokeai CVE-2024-11042" on the vendor's site.
CVE-2024-11042 (invokeai) — CWE-20 /
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: POST /api/v1/images/delete
Patched: `5.3.0rc1` — 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-20) exists in invokeai. Attackers reach the vulnerable code path via `POST /api/v1/images/delete` without authentication.
📍 Affected scope
invokeai — . Attack surface: POST /api/v1/images/delete.
🔥 Severity
Severity: ?. Data can be tampered with by attackers
🔧 How to fix
Update to **5.3.0rc1**.
🛡️ 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 /api/v1/images/delete` requests with malformed payloads or SQL meta-characters. Run `grep -r 'invokeai' .` 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 'invokeai' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `invokeai` を grep し、稼働しているサービス・バージョンを把握する。
-
3Hunt for indicators of compromise detect
grep 'POST /api/v1/images/delete' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで `POST /api/v1/images/delete` への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。
-
6Apply patch patch
Upgrade invokeai to 5.3.0rc1ステージング環境で 5.3.0rc1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Replay attack against POST /api/v1/images/delete on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
invokeai
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"5.3.0rc1"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-11042
- advisory https://github.com/advisories/GHSA-227r-w5j2-6243
- package https://github.com/invoke-ai/InvokeAI
- package https://pypi.org/project/invokeai
- web https://github.com/invoke-ai/invokeai/commit/5440c037674882b2ab7acd59087e9bb04b49657a
- web https://huntr.com/bounties/635535a7-c804-4789-ac3a-48d951263987