Envoy Proxy Envoy 1.29.1
Approved changes feed: RSS · Atom
cpe:2.3:a:envoyproxy:envoy:1.29.1:*:*:*:*:*:*:*
part: a version: 1.29.1 update: *
| Vendor | Envoyproxy (3eafc46b-a811-5a1a-8d5b-d75cdba35349) |
|---|---|
| Product | Envoy (23708333-c40f-51cb-81e4-8bbfdacbb805) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/envoyproxy/envoy |
purl2cpe | 2026-06-01 10:16:59.128463 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-27919 |
vulnerable | 2026-06-08 06:33:25.070234 |
HTTP/2: memory exhaustion due to CONTINUATION frame flood
HIGH (7.5)
Envoy is a cloud-native, open-source edge and service proxy. In versions 1.29.0 and 1.29.1, theEnvoy HTTP/2 protocol stack is vulnerable to the flood of CONTINUATION frames. Envoy's HTTP/2 codec does not reset a request when header map limits have been exceeded. This allows an attacker to send an sequence of CONTINUATION frames without the END_HEADERS bit set causing unlimited memory consumption. This can lead to denial of service through memory exhaustion. Users should upgrade to versions 1.29.2 to mitigate the effects of the CONTINUATION flood. Note that this vulnerability is a regression in Envoy version 1.29.0 and 1.29.1 only. As a workaround, downgrade to version 1.28.1 or earlier or disable HTTP/2 protocol for downstream connections.
Published: 2024-04-04T14:30:11.144Z
Updated: 2025-11-04T18:30:17.720Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.