CVE-2021-25748: high-severity vulnerability in Kubernetes ingress-nginx
Ingress-nginx `path` sanitization can be bypassed with newline character
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.6epss 0.7%
A security issue was discovered in ingress-nginx where a user that can create or update ingress objects can use a newline character to bypass the sanitization of 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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L
Affected products
Kubernetes · Kubernetes ingress-nginxRelated CVEs — Kubernetes ingress-nginx
In the same product, most dangerous first.
CVE-2021-25742HIGHIngress-nginx custom snippets allows retrieval of ingress-nginx serviceaccount token and secrets across all namespacesEPSS 2.1%CVE-2021-25746HIGHIngress-nginx directive injection via annotationsEPSS 1.4%CVE-2021-25745HIGHIngress-nginx path can be pointed to service account token fileEPSS 1.2%