GHSA-4g2f-xcph-2335
ingress-nginx has Improper Check for Unusual or Exceptional Conditions
Packages
| Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|
| Go | k8s.io/ingress-nginx | < 1.13.7 | 1.13.7 |
| Go | k8s.io/ingress-nginx | >= 1.14.0, < 1.14.3 | 1.14.3 |
Details
As written in the advisory (Markdown source, shown as plain text).
A security issue was discovered in ingress-nginx where the protection afforded by the `auth-url` Ingress annotation may not be effective in the presence of a specific misconfiguration.
If the ingress-nginx controller is configured with a default custom-errors configuration that includes HTTP errors 401 or 403, and if the configured default custom-errors backend is defective and fails to respect the X-Code HTTP header, then an Ingress with the `auth-url` annotation may be accessed even when authentication fails.
Note that the built-in custom-errors backend works correctly. Triggering this issue requires an administrator to specifically configure ingress-nginx with a broken external component.
References
External links from the advisory. They lead to third-party sites.