NGINX Gateway Fabric vulnerabilities

NGINX Gateway Fabric configured with the Gateway CRD and an authenticated gRPC connection with NGINX Agent allows a namespaced authenticated attacker with access to a service account to impersonate the authenticated NGINX Agent gRPC connection and read TLS private keys of Gateway deployments in another namespace.

Vulnerability in NGINX Gateway Fabric where the spec.basic.realm (and spec.jwt.realm) field of a namespaced AuthenticationFilter is rendered verbatim, unescaped and unvalidated, into the shared data-plane nginx.conf as auth_basic "<realm>";. An authenticated attacker with namespace access can inject arbitrary NGINX directives into the Gateway's data-plane config.

A vulnerability in NGINX Gateway Fabric where user-supplied string values from the Authentication Filter Custom Resource Definition clientID or cookieName fields, or in the clientSecret field of a Secret, are rendered directly into NGINX configuration templates without sanitization or escaping.

In NGINX Plus or NGINX Open Source configured as the data plane for NGINX Gateway Fabric, an injection vulnerability exists in the NGINX configuration generator component. User-supplied string values from the NginxProxy Custom Resource Definition access log format setting are rendered without sanitization, allowing for the injection of arbitrary NGINX configuration directives.

A vulnerability in NGINX Gateway Fabric allows an authenticated remote attacker with permission to create or modify GRPCRoute resources to cause the control plane to terminate by sending specially crafted GRPCRoute configurations containing backendRef filters.

In NGINX Gateway Fabric, when NGINX Plus is configured as the data plane, an injection vulnerability exists in the NGINX configuration generator component. User-supplied string values from the serverTokens field of the NginxProxy Custom Resource Definition and the extraAuthArgs field of the AuthenticationFilter Custom Resource Definition are rendered directly into NGINX configuration templates without sanitization or escaping. An authenticated attacker with permission to create or modify these Custom Resource Definitions may inject arbitrary NGINX configuration directives.