Browse / AI Framework and Platform Flaws / Authentication and access control
Authentication and access control
256 records in AI Framework and Platform Flaws.
- Milvus: Unauthenticated Access to Restful API on Metrics Port (9091) Leads to Critical System Compromise A metrics port exposes the full REST API without authentication, and a debug expression endpoint accepts a predictable default token.
- Khoj has an IDOR in Notion OAuth Flow that Enables Index Poisoning The Notion OAuth callback trusts an attacker-supplied state value as the target user ID, binding the attacker's integration to a victim's account.
- Lollms has an Improper Access Control vulnerability Socket.IO generation and cancel events have no authentication, so unauthenticated clients can trigger or interrupt model runs and alter shared server state.
- Lobe Chat has IDOR in Knowledge Base File Removal that Allows Cross User File Deletion A logged-in user can delete knowledge-base files owned by other users because the removal endpoint omits its ownership check.
- Chainlit contains an authorization bypass vulnerability A user-controlled key in Chainlit lets a logged-in user view or take ownership of other users' threads.
- n8n: Webhook Node IP Whitelist Bypass via Partial String Matching The n8n webhook IP whitelist used substring matching, so a client whose address merely contains a trusted entry is accepted.
- MLFlow is vulnerable to DNS rebinding attacks due to a lack of Origin header validation The REST server does not check the Origin header, so a DNS-rebinding page can call endpoints that read, change or delete experiments.
- n8n's Missing Stripe-Signature Verification Allows Unauthenticated Forged Webhooks The Stripe Trigger never checks incoming webhook requests against the stored signing secret, so anyone who knows the URL can start workflows with forged events.
- Langflow Missing Authentication on Critical API Endpoints Monitoring endpoints for messages and transactions lack the authentication dependency, so anyone can read conversation data or delete messages.
- Ollama Platform has missing authentication enabling attackers to perform model management operations Several Ollama API endpoints accept requests without authentication, so remote callers can perform model management operations.
- Langflow CORS misconfiguration enables Account Takeover and RCE Permissive CORS with credentials and a cross-site refresh cookie let a malicious page obtain fresh tokens for a logged-in victim.
- open-webui is Vulnerable to Incorrect Access Control The task-stop endpoint cancels any LLM task by ID without checking that the requesting user owns it.
- Ray's New Token Authentication is Disabled By Default Token authentication is off by default on Ray management interfaces, so a network attacker can submit jobs that run arbitrary code.
- Flowise has Authentication Bypass Using Unprotected Registration Endpoint (/register) Flowise's registration endpoint is open by default, so anyone can create an account and log in.
- Flowise does not Prevent Bypass of Password Confirmation - Unverified Password Change Authenticated users can change their password without supplying the current one, so a stolen session can take over the account.
- Flowise doesn't Prevent Bypass of Password Confirmation through Unverified Email Change (credentials) Changing the account email takes effect without verification, so an attacker can swap in a recovery address and take over the account.
- Flowise Fails to Invalidate Existing Sessions After Password Changes Existing sessions remain valid after a password change, so an attacker holding a stolen session token keeps access.
- Milvus Proxy has a Critical Authentication Bypass Vulnerability Milvus Proxy trusts a client-supplied sourceID header, so unauthenticated requests can skip authentication and gain administrative access.
- MLflow Weak Password Requirements Authentication Bypass Vulnerability Weak password requirements let remote, unauthenticated attackers get past MLflow's authentication.
- vLLM is vulnerable to timing attack at bearer auth The API key is checked with a non-constant-time string comparison, so response timing reveals correct characters and the key can be recovered incrementally.
- Flowise Cloud and Local Deployments have Unauthenticated Password Reset Token Disclosure that Leads to Account Takeover The unauthenticated forgot-password endpoint returns a valid reset token in its response, letting an attacker reset any account's password by email address.
- Langflow Vulnerable to Privilege Escalation via CLI Superuser Creation (Post-RCE) An attacker who already has code execution in the container runs the superuser CLI command, which creates an admin account without checking for an existing one.
- Lord of Large Language Models vulnerable to Observable Discrepancy attack via authenticate_user function Password comparison exits at the first mismatched character, so response timing reveals valid usernames and lets attackers guess passwords incrementally.
- n8n is vulnerable to Improper Authorization through its `/stop` endpoint The execution stop endpoint does not check workflow ownership, so an authenticated user can halt runs belonging to other users.
- LiteLLM Has an Improper Authorization Vulnerability A viewer role receives an overly privileged API key, letting it call admin endpoints and promote itself to proxy admin.
- MLflow has Weak Password Requirements Admins can create user accounts without setting a password, leaving those accounts open to anyone who can guess the username.
- Open WebUI lacks authentication for the `api/v1/utils/pdf` endpoint The PDF generation endpoint accepts requests without authentication, so anyone can submit oversized payloads that exhaust server resources.
- Open WebUI Has Improper Access Control Leading to Arbitrary Prompt Read The prompts API does not check for administrator rights, so any user can list other users' prompts and fetch them by command ID.
- Open WebUI Allows Viewing of Admin Details The admin details endpoint does not check whether the caller is an administrator, so any caller can read the first admin's account details.
- Open WebUI Allows Arbitrary File Reading and Deletion Any logged-in user can list, read and delete other users' uploaded files because the file endpoints never check for administrator rights.
- Flowise Pre-auth Arbitrary File Upload A path-prefix whitelist lets unauthenticated requests reach the attachments upload route, allowing arbitrary files to be written to local storage.
- khoj has an IDOR in subscription management allows unauthorized subscription modifications The subscription update endpoint looks up Stripe customers by a caller-supplied email and modifies their subscriptions without checking ownership.
- Letta (previously MemGPT) incorrect access control vulnerability The users endpoint of an agent memory server fails to enforce access control, exposing sensitive data to unauthorised callers.
- MLflow's excessive directory permissions allow local privilege escalation Overly broad directory permissions let a local user win a race condition and escalate privileges while spark_udf runs.
- Missing ratelimit on passwrod resets in zenml The password change endpoint has no rate limit, so an attacker can brute-force the current password and take over the account.
- Gradios's CORS origin validation is not performed when the request has a cookie Gradio skips CORS origin validation for requests carrying cookies, so a malicious site can make authenticated cross-origin requests to a local server.
- Gradio performs a non-constant-time comparison when comparing hashes The analytics dashboard compares secret hashes in non-constant time, so response timing lets an attacker recover the hash byte by byte.
- open-webui Insecure Direct Object Reference (IDOR) vulnerability The memory update endpoint checks only that a memory ID exists, not that it belongs to the caller, so users can rewrite others' stored memories.
- Flowise Authentication Bypass vulnerability Unauthenticated remote requests reach administrator-level API endpoints because access checks are missing in this version.
- TorchServe gRPC Port Exposure TorchServe binds its gRPC management and inference ports to all interfaces by default, exposing them to network clients without local restriction.
- litellm vulnerable to improper access control in team management Team management endpoints skip authorisation checks, so any caller can view, change or delete teams and their members.
- zenml-io/zenml does not expire the session after password reset Old session tokens remain valid after a password change, so a previously stolen session keeps working in another browser.
- Improper authorization in zenml Any authenticated user can update other accounts via the PUT users endpoint, including setting active to false to deactivate them.
- Improper authentication in zenml The password change endpoint skips verification of the current password, so anyone with an active session can take over the account.
- MLflow allows low privilege users to delete any artifact Users with only edit permission on an experiment can send DELETE requests that remove artifacts, which the documented permissions do not allow.
- Gradio's Component Server does not properly consider` _is_server_fn` for functions The Component Server does not check the server-function flag on functions, so non-server functions can be invoked.
- zenml Session Fixation vulnerability JWTs remain valid after logout, so a captured token can still be replayed to access the victim's session.
- Ollama DNS rebinding vulnerability DNS rebinding lets a malicious page reach the localhost-only API, exposing chat, model deletion and resource exhaustion remotely.
- ZenML Server Remote Privilege Escalation Vulnerability The user activation endpoint accepts a username plus a new password without proper authorisation, letting a remote caller take over accounts.
- Gradio apps vulnerable to timing attacks to guess password Password comparison returns at the first mismatched character, so response timing leaks progress and enables brute force because there is no rate limiting.