Coder's session token leaked to arbitrary hosts via `coder open app` for external workspace apps
coder
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/coder/coder/v2 Go |
|
|
coder
| Product | Affected | Fixed in |
|---|---|---|
| github.com/coder/coder/v2 Go |
|
|
| github.com/coder/coder Go |
| No fix yet |
Coder allows organizations to provision remote development environments via Terraform. Prior to versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2, `coder open app` opens external workspace-app URLs without validating the scheme or host. When an external app URL contains the `$SESSION_TOKEN` placeholder the CLI replaces it with the user's real session token before handing the URL to the OS open handler. Practical exploitation requires the victim to run `coder open app` against a workspace whose external app definition the attacker controls. Only a malicious template author can control external app URLs. The fix in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2 applies a URL-scheme allowlist in the CLI and limits `$SESSION_TOKEN` substitution to trusted destinations like the web frontend. As a workaround, avoid running `coder open app` for untrusted workspaces.
From the CVE record · GitHub_M
The `coder open app` CLI can put a user's session token into an external app URL without validating its scheme or host. A malicious template author who controls a workspace's external app URL could receive the token if the user runs `coder open app` against that workspace.
Check installations using Go package `github.com/coder/coder/v2` in the affected ranges (>=2.34.0 <2.34.2, >=2.33.0 <2.33.8, >=2.30.0 <2.32.7, or <2.29.17), or any version of `github.com/coder/coder`.