CSSA Exclusive Early Warning
9.9 Critical
convex-backend crafted deployment selector bypasses production authorization leading to remote privileged execution
An attacker exploits a defect in the MCP server's validation logic for the deployment selector `kind` field by constructing a non-standard production-environment selector via name or reference, thereby bypassing the security guard that applies only to `kind: "prod"`. The vulnerability allows high-risk mutation tools such as `run` and `envSet` to be invoked directly without the dangerous production-deployment flag enabled, exposing the production environment to unauthorized code execution, leakage of sensitive environment information and service-integrity compromise.
Component
convex-backend is the core backend service component of the Convex platform, designed to provide real-time data synchronization and function compute for cloud-native applications. Its architecture integrates an MCP server to support automated agent interaction, with core capabilities covering deployment management, environment-variable configuration and code execution, aiming for efficient application lifecycle management and resource scheduling.
Type
Incorrect Authorization (CWE-863)
Repo
Remediation
- Developers should refactor deployment-selector parsing so that all selector forms are normalized to the actual deployment type before the security-guard check, ensuring every request that targets production undergoes strict authorization and an explicit confirmation mechanism, eliminating authorization bypass caused by format differences.
CSSA Exclusive Early Warning
9.6 Critical
LiteLLM case-insensitive email fallback overwrites SSO/JWT subject and steals proxy administrator privileges
When the subject identifier in SSO or JWT authentication does not match the database record, the system incorrectly enables a non-strict email fuzzy-matching fallback. An attacker can exploit this defect by presenting an unverified email claim identical to an existing high-privilege account, inducing the system to bind the new malicious subject to the victim's database row and overwrite the original SSO subject identifier. Because the system lacks a second check on subject changes during role inheritance, the attacker can take over the target account's PROXY_ADMIN privileges and illicitly call sensitive management interfaces such as key generation, causing unauthorized access and potential service disruption.
Component
LiteLLM is a large-language-model routing proxy that supports multi-model access. Its core architecture is built on asynchronous Python and aims to unify API interfaces to simplify enterprise AI application integration. The component has a flexible identity-authentication module supporting protocols such as OIDC, SAML and JWT, and is responsible for user identity verification, session management and access-control policy enforcement in distributed environments to ensure security and compliance of data flow.
Type
Improper Authentication (CWE-287)
Repo
Remediation
- Remove the automated email fuzzy-matching fallback at the code level and enforce strict subject-consistency checks, allowing linking only when the email has been verified and is currently unbound. Also add role-protection for already-bound accounts, forbidding direct inheritance of high-risk administrative privileges stored in the database merely because identity-provider information is missing, thereby blocking privilege-escalation rebinding at the source.