CyberRota Analysis
AI-GeneratedThe NGINX Ingress Controller is vulnerable due to an injection flaw in its configuration generator when using Custom Resource Definitions (CRDs) or Ingress annotations, allowing authenticated attackers with write access to inject arbitrary NGINX directives. This could lead to unauthorized file manipulation, service disruption, or other control plane compromises. Organizations utilizing NGINX Ingress Controller within Kubernetes environments should prioritize patching this vulnerability to mitigate potential exploitation risks.
Original NVD Description
When NGINX Ingress Controller is configured with Custom Resource Definitions (CRDs) or Ingress annotations, an injection vulnerability exists in the configuration generator of NGINX Ingress Controller. Multiple user-controllable fields are written into the generated NGINX configuration without sanitization. An authenticated attacker with permission to create or modify these CRDs or annotations may craft values that inject arbitrary NGINX configuration directives. Impact: An authenticated attacker granted write access to NGINX Ingress Controller CRDs or Ingress annotations through the Kubernetes API may be able to inject arbitrary NGINX configuration directives, create or delete files, or disable services. There is no data plane exposure; this is a control plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Related CVEs
Other vulnerabilities affecting the same vendor(s)