← Back
CVE-2024-5225
SQL Injection in litellm (CVE-2024-5225)
Summary
SQL injection in litellm (CVE-2024-5225). Risk of unauthorized operations or information disclosure. Exploitable via ``api_key``. Mitigation: upgrade to `1.40.0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2024-5225** has been found in litellm.
Attackers can target a specific entry point like ``api_key`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade litellm to **1.40.0** or later.
If unsure, ask your IT team or search "litellm CVE-2024-5225" on the vendor's site.
CVE-2024-5225 (litellm) — CWE-89 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `api_key`
Patched: `1.40.0` — 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
**SQL injection** (CWE-89) exists in litellm. Attackers reach the vulnerable code path via ``api_key`` without authentication.
📍 Affected scope
litellm — . Attack surface: `api_key`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.40.0**.
🛡️ 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 'litellm' .` 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 'litellm' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `litellm` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade litellm to 1.40.0ステージング環境で 1.40.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
litellm
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.40.0"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2024-5225
- advisory https://github.com/advisories/GHSA-h6m6-jj8v-94jj
- package https://github.com/BerriAI/litellm
- package https://pypi.org/project/litellm
- web https://github.com/BerriAI/litellm/pull/3940
- web https://github.com/BerriAI/litellm/commit/f75c15d6cd535aa78014378ad532de1df6be2f56
- web https://huntr.com/bounties/491e4884-0306-4cd4-8fe2-9a19de33bf5c