Coder's privilege escalation vulnerability could lead to a cross workspace compromise
coder
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/coder/coder/v2 Go |
|
|
| github.com/coder/coder Go |
| No fix yet |
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. In versions 2.22.0 through 2.24.3, 2.25.0 and 2.25.1, Coder can be compromised through insecure session handling in prebuilt workspaces. Coder automatically generates a session token for a user when a workspace is started. It is automatically exposed via coder_workspace_owner.session_token. Prebuilt workspaces are initially owned by a built-in prebuilds system user. When a prebuilt workspace is claimed, a new session token is generated for the user that claimed the workspace, but the previous session token for the prebuilds user was not expired. Any Coder workspace templates that persist this automatically generated session token are potentially impacted. This is fixed in versions 2.24.4 and 2.25.2.
From the CVE record · GitHub_M
Coder does not expire the prebuilds system user's session token when a prebuilt workspace is claimed. Templates that persist the automatically generated token may leave it available for use after the claim. The input does not specify attacker authentication requirements or user interaction.
Check Coder deployments using github.com/coder/coder/v2 versions 2.22.0 through 2.24.3 or 2.25.0 through 2.25.1, and users of github.com/coder/coder, for templates that persist workspace session tokens.