Envoyproxy Envoy 1.11.2
Approved changes feed: RSS · Atom
cpe:2.3:a:envoyproxy:envoy:1.11.2:*:*:*:*:*:*:*
part: a version: 1.11.2 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.128266 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2019-15226 |
vulnerable | 2026-06-08 05:12:56.820715 |
Details available
Upon receiving each incoming request header data, Envoy will iterate over existing request headers to verify that the total size of the headers stays below a maximum limit. The implementation in versions 1.10.0 through 1.11.1 for HTTP/1.x traffic and all versions of Envoy for HTTP/2 traffic had O(n^2) performance characteristics. A remote attacker may craft a request that stays below the maximum request header size but consists of many thousands of small headers to consume CPU and result in a denial-of-service attack.
Published: 2019-10-09T15:25:02.000Z
Updated: 2024-08-05T00:42:01.230Z |
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.