Envoy Gateway up to 1.2.5 Kubernetes Cluster unprotected primary channel

Summaryinfo

A vulnerability, which was classified as problematic, has been found in Envoy Gateway up to 1.2.5. Affected is an unknown function of the component Kubernetes Cluster Handler. The manipulation leads to unprotected primary channel. This vulnerability is referenced as CVE-2025-24030. The attack needs to be initiated within the local network. No exploit is available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Envoy Gateway up to 1.2.5. This issue affects an unknown functionality of the component Kubernetes Cluster Handler. The manipulation with an unknown input leads to a unprotected primary channel vulnerability. Using CWE to declare the problem leads to CWE-419. The product uses a primary channel for administration or restricted functionality, but it does not properly protect the channel. Impacted is confidentiality, and availability. The summary by CVE is:

Envoy Gateway is an open source project for managing Envoy Proxy as a standalone or Kubernetes-based application gateway. A user with access to the Kubernetes cluster can use a path traversal attack to execute Envoy Admin interface commands on proxies managed by any version of Envoy Gateway prior to 1.2.6. The admin interface can be used to terminate the Envoy process and extract the Envoy configuration (possibly containing confidential data). Version 1.2.6 fixes the issue. As a workaround, the `EnvoyProxy` API can be used to apply a bootstrap config patch that restricts access strictly to the prometheus stats endpoint. Find below an example of such a bootstrap patch.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-24030 since 01/16/2025. The exploitation is known to be easy. The attack can only be done within the local network. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

The vulnerability scanner Nessus provides a plugin with the ID 214906 (SUSE SLES15 / openSUSE 15 Security Update : govulncheck-vulndb (SUSE-SU-2025:0297-1)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.2.6 eliminates this vulnerability. Applying the patch 3eb3301ab3dbf12b201b47bdb6074d1233be07bd is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at Tenable (214906). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• Envoy

Name

• Gateway

Version

• 1.2.0
• 1.2.1
• 1.2.2
• 1.2.3
• 1.2.4
• 1.2.5

License

• free

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion