nginx-proxy-manager/docs
Tom Winnerl 5aced8f6d0 fix(review): reject log paths that start with a request variable
`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>
2026-11-13 08:23:03 +01:00
..
.vitepress docs: host status, nginx errors and startup protection 2026-11-11 13:48:58 +01:00
scripts Docs update, use package version instead of latest, refer to better mariadb image 2026-02-19 08:36:41 +10:00
src fix(review): reject log paths that start with a request variable 2026-11-13 08:23:03 +01:00
.gitignore Migrate from vuepress to vitepress for docs site 2024-05-10 23:00:27 +10:00
package.json Docs update, use package version instead of latest, refer to better mariadb image 2026-02-19 08:36:41 +10:00
yarn.lock Update dependencies 2026-11-09 11:55:20 +10:00