Coder provider endpoint access via AI Gateway path traversal
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 |
|
|
Coder 2.28.0 before 2.29.22, 2.30.0 before 2.34.13, 2.35.0 before 2.35.10, 2.36.0 before 2.36.8, 2.37.0 before 2.37.5, and 2.38.0 before 2.38.1 contains a path traversal vulnerability in the AI Gateway passthrough router, which forwards percent-encoded dot segments upstream without rejecting them. Authenticated users can send paths such as %2e%2e or ..%2F under allowlisted prefixes to reach unintended provider endpoints using the deployment's centrally managed provider key.
From the CVE record · VulnCheck
The AI Gateway passthrough router in affected Coder versions does not reject percent-encoded dot segments in paths. An authenticated user can send a crafted path under an allowlisted prefix to reach unintended provider endpoints using the deployment’s centrally managed provider key.
Teams running Coder 2.28.0 before 2.29.22, 2.30.0 before 2.34.13, 2.35.0 before 2.35.10, 2.36.0 before 2.36.8, 2.37.0 before 2.37.5, or 2.38.0 before 2.38.1 should check their deployments.