CyberRota Analysis
AI-GeneratedEnvoy Gateway versions prior to 1.7.4 and 1.8.1 are vulnerable due to improper validation of Lua scripts, allowing attackers to exploit redundant path separators and access arbitrary files within the gateway controller pod. The impact includes potential exposure of sensitive information such as Kubernetes service-account tokens and TLS certificates, which can lead to unauthorized access to the Kubernetes API Server or Gateway xDS server. Organizations using affected versions should prioritize upgrading to the patched releases to mitigate this critical vulnerability.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. Prior to 1.7.4 and 1.8.1, to_absolute_normalized_path in internal/gatewayapi/luavalidator/security.lua does not collapse redundant separators before is_critical_path evaluates Lua submitted through EnvoyExtensionPolicy during default Strict validation. Linux resolves a double-slash absolute path as the corresponding single-slash path, but the validator does not match the redundant-separator form, allowing submitted Lua to read arbitrary files from the gateway controller pod. Exposed files can include Kubernetes service-account tokens, TLS certificates, and process environment data, and the disclosed credentials can provide access to sensitive Kubernetes API Server or Gateway xDS server information. This issue is fixed in versions 1.7.4 and 1.8.1.