A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use the spec.rules[].http.paths[].path field of an Ingress object (in the networking.k8s.io or extensions API group) to obtain the credentials of the ingress-nginx controller. In the default configuration, that credential has access to all secrets in the cluster.
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
Link | Tags |
---|---|
https://groups.google.com/g/kubernetes-security-announce/c/7vQrpDZeBlc | issue tracking mailing list mitigation third party advisory |
https://github.com/kubernetes/ingress-nginx/issues/8502 | issue tracking third party advisory mitigation |
https://security.netapp.com/advisory/ntap-20220609-0006/ | third party advisory |