Coder API key exposure in external sub-agent app URLs
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 |
|
|
The web dashboard in Coder 2.24.0 before 2.29.23, 2.30.0 before 2.34.14, 2.35.0 before 2.36.9, 2.37.0 before 2.37.6, and 2.38.0 before 2.38.2 replaces the $SESSION_TOKEN placeholder in external app URLs with a full-access API key without checking whether the app belongs to a sub-agent. Code running in a workspace can register a disguised sub-agent app with a custom protocol URL, so the owner's click sends their API key to an attacker-chosen destination.
From the CVE record · VulnCheck
The Coder web dashboard can put a full-access API key into an external app URL without checking whether the app belongs to a sub-agent. Code running in a workspace can register a disguised sub-agent app with an attacker-chosen URL; if the owner clicks it, their API key is sent to that destination.
Anyone running Coder 2.24.0 before 2.29.23, 2.30.0 before 2.34.14, 2.35.0 before 2.36.9, 2.37.0 before 2.37.6, or 2.38.0 before 2.38.2 should check their deployment.