Skip to content
Fencer Vulns
high 7.5

CVE-2024-32475 json

Envoy RELEASE_ASSERT using auto_sni with :authority header > 255 bytes

published 2024-04-18 2 y ago modified 2026-11-05 3 d ago also BIT-envoy-2024-32475 , EUVD-2024-30285 , GHSA-3mh5-6q8v-25wj

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

Summary

Envoy is a cloud-native, open source edge and service proxy. When an upstream TLS cluster is used with `auto_sni` enabled, a request containing a `host`/`:authority` header longer than 255 characters triggers an abnormal termination of Envoy process. Envoy does not gracefully handle an error when setting SNI for outbound TLS connection. The error can occur when Envoy attempts to use the `host`/`:authority` header value longer than 255 characters as SNI for outbound TLS connection. SNI length is limited to 255 characters per the standard. Envoy always expects this operation to succeed and abnormally aborts the process when it fails. This vulnerability is fixed in 1.30.1, 1.29.4, 1.28.3, and 1.27.5.

Patch / fix

  • bitnami envoy 1.27.5, 1.28.3, 1.29.4, 1.30.1
  • envoyproxy envoy 1.27.5

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-32475 updated cvss 7.5

envoy: abnormal termination when using auto_sni with authority header longer than 255 characters

  • Red Hat OpenShift Service Mesh 2 servicemesh-proxy, servicemesh-proxy-wasm
    affected: no fix planned “Will not fix”
  • Red Hat RHOSSM 2.4 for RHEL 8 openshift-service-mesh/pilot-rhel8 2.4.11-2, openshift-service-mesh/kiali-rhel8 1.65.16-4, openshift-service-mesh/grafana-rhel8 2.4.11-2, openshift-service-mesh/proxyv2-rhel8 2.4.11-5, openshift-service-mesh/istio-cni-rhel8 2.4.11-2, openshift-service-mesh/ratelimit-rhel8 2.4.11-2, +1 more
    fixed: vendor fix RHSA-2024:7724
  • 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 RHSA-2024:7725

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
none
Automatable
yes
Technical impact
partial
Assessed
2 y ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
bitnami envoy
>=1.13.0, <1.27.5
>=1.28.0, <1.28.3
>=1.29.0, <1.29.4
>=1.30.0, <1.30.1
1.27.5
1.28.3
1.29.4
1.30.1

Affected products

  • envoyproxy envoy

Classification

Weakness
  • CWE-253 Incorrect Check of Function Return Value
  • CWE-617 Reachable Assertion

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.