You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This might allow anyone, forcing in it's headers the variable X-Forwarded-For to override the real IP to anything it wants.
One side effect would be an attacker to mask it's own IP Address inside Nginx Logs. It also would allow someone to spoof it's own IP, including (but not tested) overriding the 'whitelist' restriction.
The text was updated successfully, but these errors were encountered:
phekmat
added a commit
to phekmat/ingress
that referenced
this issue
May 12, 2017
Use the same config option for `set_real_ip_from` when not using proxy protocol. The default remains `0.0.0.0/0`, which is insecure if the ingress is publicly accessible. This at least provides a workaround for kubernetes#200
In nginx.tmpl, we're using the following:
https://github.com/kubernetes/ingress/blob/master/controllers/nginx/rootfs/etc/nginx/template/nginx.tmpl#L23
set_real_ip_from 0.0.0.0/0
This might allow anyone, forcing in it's headers the variable X-Forwarded-For to override the real IP to anything it wants.
One side effect would be an attacker to mask it's own IP Address inside Nginx Logs. It also would allow someone to spoof it's own IP, including (but not tested) overriding the 'whitelist' restriction.
The text was updated successfully, but these errors were encountered: