mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-11-19 14:40:27 +00:00
`access_log $http_x;` (also `${http_x}`, `"$arg_f"`, `$cookie_c combined`, `$host$http_x`) passed the
check: a path starting with a variable returned early. nginx resolves such a path below /etc/nginx/nginx/,
so a header `X: ../../../data/nginx/proxy_host/2.conf` appended log lines to another host's config.
- A path that starts with any variable but the few that can't hold `/` or `..` is rejected; one that starts
with such a variable ($host.log) is checked as a relative path.
- Variables `set` in the same advanced configuration are replaced by each value they are set to, so
`set $p /data/logs/a.log; access_log $p;` stays allowed and `set $p $http_x; access_log $p;` is rejected.
Any other variable (set elsewhere, map, $1, ...) counts as one the client fills in.
- A request variable followed by a `/` (`$http_x.d/foo`) or `..` after any variable is rejected, and
`.npm-aside` counts as a config suffix (it becomes the .conf at startup).
Verified on nginx-full: every case of the unit tests run with steering headers, args and cookies; no
allowed case changes a .conf/.types/_params/.npm-aside/.conf.err file.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
||
|---|---|---|
| .. | ||
| .vitepress | ||
| scripts | ||
| src | ||
| .gitignore | ||
| package.json | ||
| yarn.lock | ||