ingress-nginx auth-url protection bypass
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Kubernetes | ingress-nginx | affected |
|
No data.
No data.
| Vendor | Product | Versions |
|---|---|---|
| Kubernetes | Ingress-nginx | — |
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-4g2f-xcph-2335 | ingress-nginx has Improper Check for Unusual or Exceptional Conditions |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.346% probability within 30 days)
| Link | Providers |
|---|---|
| https://github.com/kubernetes/kubernetes/issues/136679 |
|
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Kubernetes
Kubernetes ingress-nginx |
|
| Vendors & Products |
Kubernetes
Kubernetes ingress-nginx |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. To trigger this issue requires an administrator to specifically configure ingress-nginx with a broken external component. | |
| Title | ingress-nginx auth-url protection bypass | |
| Weaknesses | CWE-754 | |
| References |
| |
| Metrics |
cvssV3_1
|