# CVE-2024-4889: Code Injection in berriai/litellm

> Attackers can execute arbitrary code via malicious KMS config files if Google KMS is enabled, requiring valid configuration access.

- **Severity:** High 7.2 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-423v-966v-frxg

## What is CVE-2024-4889?

CVE-2024-4889 is a high-severity code injection vulnerability in berriai/litellm, published on 6 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A code injection vulnerability exists in the berriai/litellm application, version 1.34.6, due to the use of unvalidated input in the eval function within the secret management system. This vulnerability requires a valid Google KMS configuration file to be exploitable. Specifically, by setting the `UI_LOGO_PATH` variable to a remote server address in the `get_image` function, an attacker can write a malicious Google KMS configuration file to the `cached_logo.jpg` file. This file can then be used to execute arbitrary code by assigning malicious code to the `SAVE_CONFIG_TO_DB` environment variable, leading to full system control. The vulnerability is contingent upon the use of the Google KMS feature.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-4889?

It affects 1 product.


Products: Litellm Litellm.

## How do I fix CVE-2024-4889?

No fix has been published for CVE-2024-4889 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-4889 being exploited?

There is no known exploitation of CVE-2024-4889 in the wild and no public exploit code.

## Other vulnerabilities in berriai/litellm

- [CVE-2026-42208](https://insights.sbomify.com/CVE-2026-42208/): BerriAI LiteLLM SQL Injection (critical 9.3, exploited in the wild)
- [CVE-2026-59822](https://insights.sbomify.com/CVE-2026-59822/): BerriAI LiteLLM Improper Authentication (high 8.8, exploited in the wild)
- [CVE-2026-42271](https://insights.sbomify.com/CVE-2026-42271/): BerriAI LiteLLM Command Injection (high 8.7, exploited in the wild)
- [CVE-2024-5751](https://insights.sbomify.com/CVE-2024-5751/): Remote Code Execution in BerriAI/litellm (critical 9.8)
- [CVE-2024-2952](https://insights.sbomify.com/CVE-2024-2952/): Server-Side Template Injection in BerriAI/litellm (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-4889 and fix it if it is affected.

What it is: CVE-2024-4889 is a high-severity code injection vulnerability in berriai/litellm, published on 6 Jun 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-4889 in the wild and no public exploit code.

Affected product: berriai/litellm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-4889/ (Markdown: https://insights.sbomify.com/CVE-2024-4889/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-4889
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-4889
- OSV: https://osv.dev/vulnerability/CVE-2024-4889

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-4889/
Summaries are generated and may contain mistakes; the official description above is the record.