| ▲ | panzi 6 hours ago | |||||||
Does Debian 12 have this patched? But I guess I'm not affected if I don't use `rewrite` or `set` anywhere? | ||||||||
| ▲ | aftbit 4 hours ago | parent | next [-] | |||||||
| ▲ | wiredfool 4 hours ago | parent | prev | next [-] | |||||||
Ubuntu has patched as of this morning. Debian doesn't look like they've patched trixie yet. | ||||||||
| ||||||||
| ▲ | lpcvoid 5 hours ago | parent | prev | next [-] | |||||||
[dead] | ||||||||
| ▲ | iririririr 5 hours ago | parent | prev [-] | |||||||
I find it very unlikely that anyone using nginx does NOT use `set` at least. Most nginx use cases are to end tls and then pass the request to node/php/go/etc. So, I bet you have at least one set with attacker controller data on a line like 'proxy_set_header X-Host $host;' edit: nvm. aparently named captures are not affect. Unless you have a $1 somewhere, it should be fine. | ||||||||
| ||||||||