Sensitive data disclosure via unbound user identifier
Published Jun 6, 2024 · Updated Aug 1, 2024
SQL injection in LiteLLM 1.27.14 and earlier allows remote authenticated users to read sensitive database data via /team/update. The endpoint inserts the user_id value into a raw DELETE query rather than binding it as a parameter, so injected SQL syntax becomes part of the query. Access to a privileged team-management credential and a database-backed proxy deployment is required; exposure is limited to data readable by the database connection.
Summary
What happened
SQL injection in LiteLLM 1.27.14 and earlier allows remote authenticated users to read sensitive database data via /team/update. The endpoint inserts the user_id value into a raw DELETE query rather than binding it as a parameter, so injected SQL syntax becomes part of the query. Access to a privileged team-management credential and a database-backed proxy deployment is required; exposure is limited to data readable by the database connection.
The record
- CVE
- CVE-2024-4890
- Published
- Jun 6, 2024
- Updated
- Aug 1, 2024
- Vendor
- Berri AI
- Product
- LiteLLM
- Classifications
- CWE-89, T1190
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jun 6, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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=1.27.14
- Affected versionversion=unspecified <=latest
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
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