Veria-Labs

Name of the Vulnerable Software and Affected Versions LiteLLM versions prior to 1.83.0 Description A critical authentication bypass can occur in `LiteLLM` when JWT authentication is enabled, due to an OIDC userinfo cache key collision. The OIDC userinfo cache uses the first 20 characters of the token as the cache key. JWT headers from the same signing algorithm produce identical first 20 characters, allowing an unauthenticated attacker to craft a token that matches a legitimate user's cached token. Upon a cache hit, the attacker can inherit the legitimate user's identity and permissions. This affects deployments with JWT/OIDC authentication enabled. Recommendations Update to version 1.83.0 or later. Disable OIDC userinfo caching by setting the cache TTL to 0. Disable JWT authentication entirely.

**Name of the Vulnerable Software and Affected Versions** mppx versions prior to 0.4.11 **Description** mppx is a TypeScript interface for machine payments protocol. The `tempo/session` cooperative close handler incorrectly validated the close voucher amount using '<' instead of '<=' against the on-chain settled amount. This allowed an attacker to submit a close voucher equal to the settled amount, bypassing fund commitment and potentially closing or disrupting the channel. The vulnerable component is the `tempo/session` cooperative close handler. **Recommendations** Update to version 0.4.11 or later.

**Name of the Vulnerable Software and Affected Versions** mppx versions prior to 0.4.11 **Description** mppx is a TypeScript interface for machine payments protocol. The `stripe/charge` payment method did not validate Stripe's `Idempotent-Replayed` response header when creating PaymentIntents. This allowed an attacker to replay a valid credential containing the same `spt` token against a new challenge, and the server would accept the replayed Stripe PaymentIntent as a new successful payment without actually charging the customer again. This enabled an attacker to pay once and consume unlimited resources by replaying the credential. The affected API endpoint is the `stripe/charge` payment method. **Recommendations** Update to version 0.4.11 or later.