Authorization Bypass Through User-Controlled Key Affecting envoyproxy/envoy package, versions [,1.28.7)[1.29.0,1.29.9)[1.30.0,1.30.6)[1.31.0,1.31.2)
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Authorization Bypass Through User-Controlled Key vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-UNMANAGED-ENVOYPROXYENVOY-8062353
- published20 Sept 2024
- disclosed19 Sept 2024
- creditJames Force, Mike Whale
Introduced: 19 Sep 2024
CVE-2024-45806 (opens in a new tab)How to fix?
Upgrade envoyproxy/envoy to version 1.28.7, 1.29.9, 1.30.6, 1.31.2 or higher.
Overview
Affected versions of this package are vulnerable to Authorization Bypass Through User-Controlled Key due to the default configuration of internal trust boundaries. An attacker can bypass security controls and access sensitive data or disrupt services within the mesh by manipulating x-envoy headers from external sources. This is only exploitable if the internal_address_config is empty or improperly configured.
PoC
With a default edge ingress Envoy configured.
$ curl -k -H "X-ENVOY-ORIGINAL-PATH: /foobar" https://bookinfo-bookinfo.apps.test.cluster.net/productpageX-ENVOY-ORIGINAL-PATHis trusted.