Coder privilege escalation in API key creation
coder
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| coder coder |
|
|
| coder coder |
|
|
| coder coder |
|
|
coder
| Product | Affected | Fixed in |
|---|---|---|
| coder coder |
|
|
| coder coder |
|
|
| coder coder |
|
|
| coder coder |
|
|
| coder coder |
|
|
| coder coder |
|
|
Coder 2.28.0 before 2.29.24, 2.30.0 before 2.34.16, 2.35.0 before 2.36.11, 2.37.0 before 2.37.8, and 2.38.0 before 2.38.4 does not restrict new API keys to the creating token's scopes, allow list, or expiry. A scoped API key or OAuth2 token holding key-creation permission can call POST /api/v2/users/{user}/keys/tokens to mint longer-lived coder:all keys, gaining the user's full privileges.
From the CVE record · VulnCheck
Affected Coder versions do not restrict new API keys to the creating token’s scopes, allow list, or expiry. An attacker holding a scoped API key or OAuth2 token with key-creation permission can use the API to create a longer-lived coder:all key and gain the user’s full privileges.
Operators running Coder 2.28.0 before 2.29.24, 2.30.0 before 2.34.16, 2.35.0 before 2.36.11, 2.37.0 before 2.37.8, or 2.38.0 before 2.38.4 should check their installations.