REDHAT-BUG-2455509: High severity LiteLLM LiteLLM vulnerability
LiteLLM is a proxy server (AI Gateway) to call LLM APIs in OpenAI (or native) format. Prior to 1.83.0, when JWT authentication is enabled (enablejwtauth: true), the OIDC userinfo cache uses token[:20] as the cache key. JWT headers produced by the same signing algorithm generate identical first 20 characters. This configuration option is not enabled by default. Most instances are not affected. An unauthenticated attacker can craft a token whose first 20 characters match a legitimate user's cached token. On cache hit, the attacker inherits the legitimate user's identity and permissions. This affects deployments with JWT/OIDC authentication enabled. Fixed in v1.83.0.
Affected Software
Event History
Frequently Asked Questions
What is the severity of REDHAT-BUG-2455509?
The severity of REDHAT-BUG-2455509 is critical due to potential JWT authentication bypass risks.
How do I fix REDHAT-BUG-2455509?
To fix REDHAT-BUG-2455509, upgrade LiteLLM to version 1.83.0 or later.
What issues arise from REDHAT-BUG-2455509?
REDHAT-BUG-2455509 may lead to unauthorized access through JWT token collision.
Who is affected by REDHAT-BUG-2455509?
Only users of LiteLLM versions prior to 1.83.0 with JWT authentication enabled are affected by REDHAT-BUG-2455509.
What is the nature of the vulnerability in REDHAT-BUG-2455509?
The vulnerability in REDHAT-BUG-2455509 arises from the usage of similar JWT headers resulting in identical cache keys.