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