Impact
Coder allows organizations to provision remote development environments via Terraform. In versions prior to 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3, the azureidentity.Validate() function checks that the PKCS#7 signer certificate chains to a trusted Azure CA, but it never verifies the PKCS#7 signature itself. An attacker can embed a legitimate Azure certificate together with arbitrary data, such as a forged "vmId":"<target>", and the forged vmId will be accepted, causing the victim's workspace agent session token to be returned. No authentication is required; the attacker only needs to know the target VM's vmId, which is a UUIDv4, a limitation that typically means prior access is needed.
Affected Systems
All Coder releases prior to the patched versions 2.24.5, 2.29.13, 2.30.8, 2.31.12, 2.32.2, and 2.33.3 are affected. The vulnerability specifically impacts the Azure instance identity feature used during Terraform provisioning; any environment that relies on this integration while running an affected Coder version is at risk.
Risk and Exploitability
The CVSS score of 9.1 highlights the high severity of unauthenticated token theft with remote impact. Because the vulnerability does not require user interaction or authentication, an attacker who knows a legitimate VM UUIDv4 can craft a malicious PKCS#7 payload from any network location. The EPSS score of < 1% indicates that, despite the high impact, the current probability of exploitation remains low, possibly requiring the attacker to already have some level of access or to discover a valid UUIDv4. The flaw is not listed in the CISA KEV catalog. Administrators should treat it as a critical risk until the affected releases are updated.
OpenCVE Enrichment
Github GHSA