From 9395d19333dbda508cbea83943cc551f2289be66 Mon Sep 17 00:00:00 2001 From: kisfenyo Date: Thu, 1 Oct 2026 21:02:58 +0200 Subject: [PATCH] emby: remove the client-written X-Forwarded-For chain on its router (R-753) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit leftmost XFF decides who is on the LAN (remote-access and IP-filter bypass). Once traefik trusts the tunnel's fixed address (controller v0.286.0), the leftmost entry is what a stranger writes; with the chain removed the app reads traefik's X-Real-Ip or its peer, as before — never forgeable. Measured on 9202: a router with this middleware receives no X-Forwarded-For (felhom.eu audits/visitors-2026-10-01/A/P1). Co-Authored-By: Claude Opus 5.5 (1M context) Claude-Session: https://claude.ai/code/session_0159rPz1ZhFKsS53msqPYxtS --- templates/emby/docker-compose.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/templates/emby/docker-compose.yml b/templates/emby/docker-compose.yml index b56957a..d7dab2f 100644 --- a/templates/emby/docker-compose.yml +++ b/templates/emby/docker-compose.yml @@ -40,6 +40,10 @@ services: labels: - "traefik.enable=true" - "traefik.http.routers.emby.rule=Host(`${SUBDOMAIN}.${DOMAIN}`)" + # R-753: this app reads the LEFTMOST X-Forwarded-For entry, which a stranger writes once traefik keeps the + # tunnel's chain — so its chain is removed here (it then reads traefik's X-Real-Ip or peer; never forgeable). + - "traefik.http.middlewares.emby-xff.headers.customrequestheaders.X-Forwarded-For=" + - "traefik.http.routers.emby.middlewares=emby-xff" - "traefik.http.routers.emby.entrypoints=websecure" - "traefik.http.routers.emby.tls=true" - "traefik.http.routers.emby.tls.certresolver=letsencrypt"