Coder's OIDC email_verified type coercion bypass enables account takeover via unverified email linking
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's OIDC callback checked `email_verified` with a direct Go `bool` type assertion. When an IdP returned the claim as a non-boolean (for example the string `"false"`) or omitted it, the assertion failed open and the email was treated as verified. Combined with an unconditional email-based account fallback, this enabled account takeover. The fix in versions 2.29.7, 2.32.7, 2.33.8, and 2.34.2 coerces `email_verified` across bool, string and numeric types (fail-closed) and blocks the email fallback when the matched user already has a different linked IdP subject. As a workaround, ensure the IdP returns `email_verified` as a native JSON boolean. The email-fallback linking issue has no configuration workaround; upgrading is required.
From the CVE record · GitHub_M
Coder's OIDC callback can treat a missing or non-boolean `email_verified` claim as verified. When an IdP supplies such a claim and email-based account fallback matches an existing user, an attacker can take over that account. The input does not specify whether prior authentication or user interaction is required.
Teams running affected versions of Go package github.com/coder/coder/v2, or any version of github.com/coder/coder, should check their deployments.