Suspended Coder users retain access to AI Bridge LLM proxy endpoints
coder
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/coder/coder/v2 Go |
|
|
| github.com/coder/coder Go |
coder
| Product | Affected | Fixed in |
|---|---|---|
| github.com/coder/coder/v2 Go |
|
|
| github.com/coder/coder Go |
all versions| No fix yet |
Coder allows organizations to provision remote development environments via Terraform. Starting in version 2.30.0 and prior to versions 2.32.7, 2.33.8, and 2.34.2, AI Bridge proxy endpoints authenticate via `Server.IsAuthorized` in `coderd/aibridgedserver`, which validates key format, expiry, secret and deleted or system users but does not check whether the account is suspended. Because suspension does not revoke existing API keys, a suspended user's unexpired token keeps working. Practical impact is limited to already-issued API keys of suspended users until those keys are deleted. Versions 2.32.7, 2.33.8, and 2.34.2 patch the issue. As a workaround, on suspension, delete the user's API keys via `DELETE /api/v2/users/{user}/keys`.
From the CVE record · GitHub_M
Coder's AI Bridge proxy endpoints do not check whether an account is suspended. A suspended user can continue using an already-issued, unexpired API key until that key is deleted; no user interaction is required.
Teams running Go package github.com/coder/coder/v2 in versions >=2.30.0 <2.32.7, >=2.33.0 <2.33.8, or >=2.34.0 <2.34.2, or github.com/coder/coder at any version, should check their deployments.