This Week in Security: IngressNightmare, NextJS, and Leaking DNA
1 min read
Summary
In a new report this week researchers revealed several vulnerabilities in the Kubernetes Ingress NGINX Controller that, when exploited, allow an attacker to take over a targeted cluster.
The Ingress controller is a popular routing solution for web applications running on Kubernetes, converting Kubernetes Ingress objects into NGINX config and running the admission controller to test.
The Wiz Research team discovered multiple vulnerabilities that allow raw NGINX config statements to be passed through into the config to be tested, and the can be used for remote code execution.
The issue was fixed in Ingress NGINX Controller version 1.12.1 and 1.11.5, but Kubernetes installs using the Ingress NGINX Controller are still at risk if they haven’t updated.
Another issue affecting the middleware component of Next.js, a web application framework, that serves a similar function to an ingress controller, has also been highlighted this week.
The Next.js middleware layer just passes the request without processing if a valid x-middleware-subrequest header is spoofed, but this can be used to bypass authentication.
