Caddy: vars_regexp double-expands user input, leaking env vars and files
caddyserver caddy
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/caddyserver/caddy/v2/modules/caddyhttp Go |
|
|
| github.com/caddyserver/caddy/v2 Go |
|
|
caddyserver caddy
| Product | Affected | Fixed in |
|---|---|---|
| github.com/caddyserver/caddy/v2/modules/caddyhttp Go |
|
|
| github.com/caddyserver/caddy/v2 Go |
|
|
Caddy is an extensible server platform that uses TLS by default. From version 2.7.5 to before version 2.11.2, the vars_regexp matcher in vars.go:337 double-expands user-controlled input through the Caddy replacer. When vars_regexp matches against a placeholder like {http.request.header.X-Input}, the header value gets resolved once (expected), then passed through repl.ReplaceAll() again (the bug). This means an attacker can put {env.DATABASE_URL} or {file./etc/passwd} in a request header and the server will evaluate it, leaking environment variables, file contents, and system info. This issue has been patched in version 2.11.2.
From the CVE record · GitHub_M
Caddy's vars_regexp matcher double-expands user-controlled input when it matches a placeholder such as a request header. An attacker who can send a crafted request header to a server using this matcher can cause Caddy to evaluate placeholders that may expose environment variables, file contents, or system information.
Check Caddy deployments and Go packages github.com/caddyserver/caddy/v2 and github.com/caddyserver/caddy/v2/modules/caddyhttp at versions 2.7.5 through versions before 2.11.2.