CVE-2024-45806
"Envoy Untrusted Internal Address Header Manipulation"
Description
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.
INFO
Published Date :
Sept. 20, 2024, 12:15 a.m.
Last Modified :
Oct. 15, 2024, 4:03 p.m.
Source :
[email protected]
Remotely Exploitable :
Yes !
Impact Score :
2.5
Exploitability Score :
3.9
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2024-45806.
| URL | Resource |
|---|---|
| https://github.com/envoyproxy/envoy/security/advisories/GHSA-ffhv-fvxq-r6mf | Third Party Advisory |
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2024-45806 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2024-45806 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
Reanalysis by [email protected]
Oct. 15, 2024
Action Type Old Value New Value Removed CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Added CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N -
Reanalysis by [email protected]
Oct. 03, 2024
Action Type Old Value New Value Removed CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Added CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N -
Initial Analysis by [email protected]
Sep. 25, 2024
Action Type Old Value New Value Added CVSS V3.1 NIST AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Changed Reference Type https://github.com/envoyproxy/envoy/security/advisories/GHSA-ffhv-fvxq-r6mf No Types Assigned https://github.com/envoyproxy/envoy/security/advisories/GHSA-ffhv-fvxq-r6mf Third Party Advisory Added CWE NIST CWE-639 Added CPE Configuration OR *cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:* versions up to (excluding) 1.28.7 *cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:* versions from (including) 1.29.0 up to (excluding) 1.29.9 *cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:* versions from (including) 1.30.0 up to (excluding) 1.30.6 *cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:* versions from (including) 1.31.0 up to (excluding) 1.31.2 -
CVE Received by [email protected]
Sep. 20, 2024
Action Type Old Value New Value Added Description 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. Added Reference GitHub, Inc. https://github.com/envoyproxy/envoy/security/advisories/GHSA-ffhv-fvxq-r6mf [No types assigned] Added CWE GitHub, Inc. CWE-639 Added CVSS V3.1 GitHub, Inc. AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2024-45806 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2024-45806
weaknesses.