Proxy crash via literal request-body parsing
Published Mar 20, 2025 · Updated Mar 20, 2025
Uncontrolled resource consumption in LiteLLM before 1.53.1 allows remote attackers to crash its Python proxy with a crafted request. The _read_request_body function in http_parsing_utils.py passes the decoded HTTP body to ast.literal_eval before attempting JSON parsing. No authentication or user interaction is required, and successful exploitation interrupts requests served by the crashed process.
Summary
What happened
Uncontrolled resource consumption in LiteLLM before 1.53.1 allows remote attackers to crash its Python proxy with a crafted request. The _read_request_body function in http_parsing_utils.py passes the decoded HTTP body to ast.literal_eval before attempting JSON parsing. No authentication or user interaction is required, and successful exploitation interrupts requests served by the crashed process.
The record
- CVE
- CVE-2024-10188
- Published
- Mar 20, 2025
- Updated
- Mar 20, 2025
- Vendor
- Berri AI
- Product
- LiteLLM
- Classifications
- CWE-400, T1499
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 20, 2025CVE publishedPublication date reported by the CVE source.
- Mar 20, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <1.53.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo