Browse / AI Framework and Platform Flaws / GHSA-g5ff-637f-6q2m
LiteLLM: internal_user_viewer arbitrary local file read via `vertex_ai_credentials`
- Class
- AI Framework and Platform Flaws (filed by a model that read the advisory)
- Technique
- Path traversal and file access
- Also involves
- Sensitive Data Disclosure
- Affected
- litellm (PyPI)
- Gets past
- Input filter or sanitiser
- CVSS
- CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
How it works, in short
An authenticated viewer sends an alias of a credentials field that the request blocklist misses, so a local file is read and sent out. (Our summary, written by a model. The source text is below.)
Details
Summary
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.
References
- https://github.com/BerriAI/litellm/security/advisories/GHSA-g5ff-637f-6q2m
- https://github.com/BerriAI/litellm/pull/34189
- https://github.com/BerriAI/litellm/commit/065faf6e695be64a1a367601271839914e4a6621
- https://github.com/BerriAI/litellm
- https://github.com/BerriAI/litellm/releases/tag/v1.95.0
Source: GitHub Advisory Database, used under CC BY 4.0.