CVE-2024-45806: Envoy is a cloud-native high-performance edge/middle/service proxy.
Medium CVSS 6.5
- CVE id
- CVE-2024-45806
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Envoy Runtimes and servers |
< 1.28.7 >= 1.29.0, < 1.29.9 >= 1.30.0, < 1.30.6 >= 1.31.0, < 1.31.2 |
1.28.7, 1.29.9, 1.30.6, 1.31.2 |
How to fix it
Upgrade Envoy to the fixed release of the line you run: 1.28.7, 1.29.9, 1.30.6, 1.31.2.
envoy --version
- Upgrade Envoy (the envoyproxy/envoy image tag) to the patched release.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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 internaladdressconfig 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.
References
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.