API-key theft via caller-controlled provider URL
Published Sep 13, 2024 · Updated Sep 13, 2024
SSRF in Berri AI LiteLLM before 1.44.9 allows remote attackers to steal an OpenAI API key through a crafted chat request. The proxy's POST /chat/completions handler accepts api_base or base_url from the request body and uses it as the provider destination without restricting caller-controlled routing. Unauthenticated network access to that endpoint is sufficient, and the outbound request discloses the configured OpenAI API key to the chosen host.
Summary
What happened
SSRF in Berri AI LiteLLM before 1.44.9 allows remote attackers to steal an OpenAI API key through a crafted chat request. The proxy's POST /chat/completions handler accepts api_base or base_url from the request body and uses it as the provider destination without restricting caller-controlled routing. Unauthenticated network access to that endpoint is sufficient, and the outbound request discloses the configured OpenAI API key to the chosen host.
The record
- CVE
- CVE-2024-6587
- Published
- Sep 13, 2024
- Updated
- Sep 13, 2024
- Vendor
- Berri AI
- Product
- LiteLLM
- Classifications
- CWE-918, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 13, 2024CVE publishedPublication date reported by the CVE source.
- Sep 13, 2024Record 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=0 <1.44.9
- Affected versionversion=unspecified <1.44.9
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.
Weakness, pattern, technique
Public exploit references
- huntr LiteLLM SSRF bounty artifactproof of concept · unverified
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