LiteLLM: internal_user_viewer arbitrary local file read via `vertex_ai_credentials`
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- The rating the maker of the software gives it. Shown when it differs from the CVSS level.What do these mean? →
- High (ghsa)
- Fix
- Fixed in 1.95.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
LiteLLM proxy deployments are affected, specifically the request handling for the Vertex AI credential parameter. An authenticated low-privilege user can exploit this to read arbitrary files on the proxy server, which can expose secrets such as master keys and provider API keys and potentially lead to full administrative control of the proxy.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
An authenticated LiteLLM proxy user could read arbitrary local files from the proxy runtime by sending a crafted `vertex_ai_credentials` value to `/utils/transform_request`. The request-body safety blocklist rejected `vertex_credentials` but missed its alias `vertex_ai_credentials`, which let the value reach the Vertex AI credential loader and trigger a file read that is sent to an attacker-controlled URL. Impact A low-privilege authenticated user (only `internal_user_viewer`, obtainable through SSO login on many deployments) could read any file readable by the LiteLLM process. Reading files such as `/proc/self/environ` can disclose `LITELLM_MASTER_KEY` and provider API keys, so the impact can escalate to full proxy-admin control. Remediation Upgrade to `1.95.0` or later. The fix adds the missing alias to the request-body blocklist, so no configuration change is needed once you upgrade. There is no reliable configuration workaround on affected versions.
Timeline
- Advisory published
- Record last updated
- First seen by cve.now
Affected versions
- litellmPyPI
fixed in 1.95.0