Envoy Proxy Envoy 1.30.0
Approved changes feed: RSS · Atom
cpe:2.3:a:envoyproxy:envoy:1.30.0:*:*:*:*:*:*:*
part: a version: 1.30.0 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.128482 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-39305 |
vulnerable | 2026-06-08 06:41:49.029089 |
Envoy Proxy use after free when route hash policy is configured with cookie attributes
MEDIUM (6.5)
Envoy is a cloud-native, open source edge and service proxy. Prior to versions 1.30.4, 1.29.7, 1.28.5, and 1.27.7. Envoy references already freed memory when route hash policy is configured with cookie attributes. Note that this vulnerability has been fixed in the open as the effect would be immediately apparent if it was configured. Memory allocated for holding attribute values is freed after configuration was parsed. During request processing Envoy will attempt to copy content of de-allocated memory into request cookie header. This can lead to arbitrary content of Envoy's memory to be sent to the upstream service or abnormal process termination. This vulnerability is fixed in Envoy versions v1.30.4, v1.29.7, v1.28.5, and v1.27.7. As a workaround, do not use cookie attributes in route action hash policy.
Published: 2024-07-01T21:10:23.566Z
Updated: 2024-08-02T04:19:20.740Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-32475 |
vulnerable | 2026-06-08 06:35:33.184787 |
Envoy RELEASE_ASSERT using auto_sni with :authority header > 255 bytes
HIGH (7.5)
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.
Published: 2024-04-18T14:18:18.947Z
Updated: 2024-08-02T02:13:39.139Z |
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.