Skip to content
Noroxi
CVE-2024-32974· NVD / CVE Program· CNA GitHub_M

Envoy affected by a crash in EnvoyQuicServerStream::OnInitialHeadersComplete()

Envoy is a cloud-native, open source edge and service proxy. A crash was observed in `EnvoyQuicServerStream::OnInitialHeadersComplete()` with following call stack. It is a use-after-free caused by QUICHE continuing push request headers after `StopReading()` being called on the stream. As after `StopReading()`, the HCM's `ActiveStream` might have already be destroyed and any up calls from QUICHE could potentially cause use after free.

HighCVSS 7.5 · v3.1—No exploit No fix recorded
Published
Jun 4, 2024
Updated
Jun 17, 2026
EPSS
0.7% · 51th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.7%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · GitHub_M
5.9
1.6 point gap

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
envoyproxyenvoy

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • envoyproxy envoybefore 1.27.6
  • envoyproxy envoy1.28.0 and later · before 1.28.4
  • envoyproxy envoy1.29.0 and later · before 1.29.5
  • envoyproxy envoy1.30.0 and later · before 1.30.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • envoyproxy envoy

    • >= 1.30.0, <= 11.30.1, >= 1.29.0, <= 1.29.4, >= 1.28.0, <= 1.28.3, <= 1.27.5affected

Same product

envoyproxy: all records

Other highest-scoring records for the same primary product.

  • CVE-2024-30255HTTP/2: CPU exhaustion due to CONTINUATION frame flood
    56Plan
  • CVE-2024-27919HTTP/2: memory exhaustion due to CONTINUATION frame flood
    56Plan
  • CVE-2021-29492Bypass of path matching rules using escaped slash characters
    53Plan
  • CVE-2019-15226Upon receiving each incoming request header data, Envoy will iterate over existing request headers to verify that the total size of the head
    49Plan
  • CVE-2019-9901Envoy 1.9.0 and before does not normalize HTTP URL paths.
    41Plan
  • CVE-2019-18802An issue was discovered in Envoy 1.12.0.
    40Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2024-3930527 days apartEnvoy Proxy use after free when route hash policy is configured with cookie attributes
    36Monitor
  • CVE-2024-23322116 days apartEnvoy crashes when idle and request per try timeout occur within the backoff interval
    30Monitor
  • CVE-2023-35943315 days apartEnvoy vulnerable to CORS filter segfault when origin header is removed
    30Monitor
  • CVE-2025-54588455 days apartEnvoy: Race condition in Dynamic Forward Proxy leads to use-after-free and segmentation faults
    30Monitor
  • CVE-2025-62504499 days apartEnvoy Lua filter use-after-free when oversized rewritten response body causes crash
    30Monitor
  • CVE-2023-35942315 days apartEnvoy's gRPC access log crash caused by the listener draining
    26Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-416 · Use After Free

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Root cause

After a memory region is freed, another reference pointing to it is still used. By then, the same region may have been allocated for different data.

The bug in code

The whole CWE-416 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

c
free(dev->buf);/* ... another thread is still running ... */process(dev->buf);

Fixed

c
lock(&dev->lock);free(dev->buf);dev->buf = NULL;unlock(&dev->lock);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.

All records