Skip to content
Fencer Vulns
high 7.5

CVE-2024-23325 json

Envoy crashes when using an address type that isn’t supported by the OS

published 2024-02-09 2 y ago modified 2026-09-08 2 mo ago also BIT-envoy-2024-23325 , EUVD-2024-20840 , GHSA-5m7c-mrwr-pm26

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

Summary

Envoy is a high-performance edge/middle/service proxy. Envoy crashes in Proxy protocol when using an address type that isn’t supported by the OS. Envoy is susceptible to crashing on a host with IPv6 disabled and a listener config with proxy protocol enabled when it receives a request where the client presents its IPv6 address. It is valid for a client to present its IPv6 address to a target server even though the whole chain is connected via IPv4. This issue has been addressed in released 1.29.1, 1.28.1, 1.27.3, and 1.26.7. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Patch / fix

  • bitnami envoy 1.26.7, 1.27.3, 1.28.1, 1.29.1
  • envoyproxy envoy 1.26.7, 1.27.3, 1.28.1, 1.29.1

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-23325 updated cvss 5.9

envoy: Envoy crashes when using an address type that isn’t supported by the OS

  • Red Hat OpenShift Service Mesh 2 servicemesh-proxy, servicemesh-proxy-wasm, openshift-service-mesh/proxyv2-rhel8
    affected: no fix available

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.75% chance of exploitation in the next 30 days, higher than 55% 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
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.26.0, <1.26.7
>=1.27.0, <1.27.3
>=1.28.0, <1.28.1
>=1.29.0, <1.29.1
1.26.7
1.27.3
1.28.1
1.29.1

Affected products

  • envoyproxy envoy

Classification

Weakness
  • CWE-755 Improper Handling of Exceptional Conditions
  • CWE-248 Uncaught Exception

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.