zrok has reflected XSS in GitHub OAuth callback via unsanitized refreshInterval error rendering
openziti zrok
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/openziti/zrok Go |
| No fix yet |
| github.com/openziti/zrok/v2 Go |
|
|
openziti zrok
| Product | Affected | Fixed in |
|---|---|---|
| github.com/openziti/zrok Go |
| No fix yet |
| github.com/openziti/zrok/v2 Go |
|
|
zrok is software for sharing web services, files, and network resources. Prior to version 2.0.1, the proxyUi template engine uses Go's text/template (which performs no HTML escaping) instead of html/template. The GitHub OAuth callback handlers in both publicProxy and dynamicProxy embed the attacker-controlled refreshInterval query parameter verbatim into an error message when time.ParseDuration fails, and render that error unescaped into HTML. An attacker can deliver a crafted login URL to a victim; after the victim completes the GitHub OAuth flow, the callback page executes arbitrary JavaScript in the OAuth server's origin. Version 2.0.1 patches the issue.
From the CVE record · GitHub_M
zrok’s proxyUi renders an attacker-controlled query parameter into HTML without escaping it when duration parsing fails. An attacker can send a crafted login URL that executes JavaScript in the OAuth server’s origin after the victim completes the GitHub OAuth flow.
Check deployments using Go package github.com/openziti/zrok/v2 before 2.0.1 or github.com/openziti/zrok at version 1.1.11 or earlier.