Envoy up to 1.28.6/1.29.4/1.30.0 internal_address_config authorization

Summaryinfo

A vulnerability classified as critical was found in Envoy up to 1.28.6/1.29.4/1.30.0. This issue affects some unknown processing. Executing a manipulation of the argument internal_address_config can lead to authorization. The identification of this vulnerability is CVE-2024-45806. The attack may be launched remotely. There is no exploit available. Upgrading the affected component is advised.

Detailsinfo

A vulnerability has been found in Envoy up to 1.28.6/1.29.4/1.30.0 and classified as critical. This vulnerability affects an unknown function. The manipulation of the argument internal_address_config with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:

Envoy is a cloud-native high-performance edge/middle/service proxy. A security vulnerability in Envoy allows external clients to manipulate Envoy headers, potentially leading to unauthorized access or other malicious actions within the mesh. This issue arises due to Envoy's default configuration of internal trust boundaries, which considers all RFC1918 private address ranges as internal. The default behavior for handling internal addresses in Envoy has been changed. Previously, RFC1918 IP addresses were automatically considered internal, even if the internal_address_config was empty. The default configuration of Envoy will continue to trust internal addresses while in this release and it will not trust them by default in next release. If you have tooling such as probes on your private network which need to be treated as trusted (e.g. changing arbitrary x-envoy headers) please explicitly include those addresses or CIDR ranges into `internal_address_config`. Successful exploitation could allow attackers to bypass security controls, access sensitive data, or disrupt services within the mesh, like Istio. This issue has been addressed in versions 1.31.2, 1.30.6, 1.29.9, and 1.28.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.

The advisory is available at github.com. This vulnerability was named CVE-2024-45806 since 09/09/2024. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit.

The vulnerability scanner Nessus provides a plugin with the ID 210925 (Amazon Linux 2 : ecs-service-connect-agent (ALASECS-2024-045)), which helps to determine the existence of the flaw in a target environment.

Upgrading to version 1.28.7, 1.29.5 or 1.30.1 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at Tenable (210925). If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

• Envoy

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.23
• 1.24
• 1.25
• 1.26
• 1.27
• 1.28
• 1.28.0
• 1.28.1
• 1.28.2
• 1.28.3
• 1.28.4
• 1.28.5
• 1.28.6
• 1.29
• 1.29.0
• 1.29.1
• 1.29.2
• 1.29.3
• 1.29.4
• 1.30.0

License

• free

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Discussion