Skip to content
Fencer Vulns
medium 6.5

CVE-2024-45806 json

Potential manipulate `x-envoy` headers from external sources in envoy

published 2024-09-19 2 y ago modified 2026-09-08 2 mo ago also BIT-envoy-2024-45806 , EUVD-2024-41611 , GHSA-ffhv-fvxq-r6mf

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 31%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami envoy 1.28.7, 1.29.9, 1.30.6, 1.31.2
  • envoyproxy envoy 1.28.7, 1.29.9, 1.30.6, 1.31.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-45806 updated cvss 7.4

envoy: Potential to manipulate `x-envoy` headers from external sources

  • Red Hat RHOSSM 2.5 for RHEL 8 openshift-service-mesh/pilot-rhel8 2.5.5-4, openshift-service-mesh/grafana-rhel8 2.5.5-3, openshift-service-mesh/kiali-rhel8 1.73.15-3, openshift-service-mesh/proxyv2-rhel8 2.5.5-6, openshift-service-mesh/istio-cni-rhel8 2.5.5-4, openshift-service-mesh/ratelimit-rhel8 2.5.5-3, +2 more
    fixed: vendor fix “This flaw can be mitigated by configuring envoy to treat all IPs as external. This is done by setting the internal_address_config range for envoy to `0.0.0.0/32`.” RHSA-2024:7725
  • Red Hat RHOSSM 2.6 for RHEL 8 openshift-service-mesh/pilot-rhel8 2.6.2-5, openshift-service-mesh/kiali-rhel8 1.89.4-3, openshift-service-mesh/grafana-rhel8 2.6.2-3, openshift-service-mesh/istio-cni-rhel8 2.6.2-5, openshift-service-mesh/ratelimit-rhel8 2.6.2-3, openshift-service-mesh/kiali-ossmc-rhel8 1.89.2-3, +3 more Red Hat RHOSSM 2.6 for RHEL 9 openshift-service-mesh/proxyv2-rhel9 2.6.2-7
    fixed: vendor fix “This flaw can be mitigated by configuring envoy to treat all IPs as external. This is done by setting the internal_address_config range for envoy to `0.0.0.0/32`.” RHSA-2024:7726

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.38% chance of exploitation in the next 30 days, higher than 31% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
bitnami envoy
<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

Affected products

  • envoyproxy envoy

Classification

Weakness
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.