Skip to content
Fencer Vulns
medium 6.5

CVE-2024-45810 json

Envoy crashes for LocalReply in http async client

published 2024-09-19 2 y ago modified 2026-09-08 2 mo ago also BIT-envoy-2024-45810 , EUVD-2024-41615 , GHSA-qm74-x36m-555q

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

Summary

Envoy is a cloud-native high-performance edge/middle/service proxy. Envoy will crash when the http async client is handling `sendLocalReply` under some circumstance, e.g., websocket upgrade, and requests mirroring. The http async client will crash during the `sendLocalReply()` in http async client, one reason is http async client is duplicating the status code, another one is the destroy of router is called at the destructor of the async stream, while the stream is deferred deleted at first. There will be problems that the stream decoder is destroyed but its reference is called in `router.onDestroy()`, causing segment fault. This will impact ext_authz if the `upgrade` and `connection` header are allowed, and request mirrorring. 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.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-45810 updated cvss 7.5

envoy: Envoy crashes for `LocalReply` in HTTP async client

  • Red Hat OpenShift Service Mesh 2 openshift-service-mesh/proxyv2-rhel8
    affected: workaround, no fix available
  • 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 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
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

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

Exploits and checks

  • github.com https://github.com/envoyproxy/envoy/security/advisories/GHSA-qm74-x36m-555q referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 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.31.2
1.31.2

Affected products

  • envoyproxy envoy

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

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.