Skip to content

Lua modified large enough response body will cause Envoy to crash

Moderate
phlax published GHSA-gcxr-6vrp-wff3 Oct 16, 2025

Package

Envoy (Envoy proxy)

Affected versions

<= 1.36.1

Patched versions

1.36.2 1.35.6 1.34.10 1.33.12

Description

Summary

When Lua directly returns an oversized response body exceeding the per_connection_buffer_limit_bytes (default 1MB), Envoy will crash directly.

Details

A Use-After-Free vulnerability exists in the Envoy proxy's Lua filter. The vulnerability is triggered when a Lua script, executing during the response phase, rewrites a response body to a size that exceeds the configured buffer watermark, resulting in a local reply. The direct local response headers will override the original response headers and result in all references of original response headers be dangling.

Mitigation

  • We can increase per_connection_buffer_limit_bytes to a large enough value to avoid it.
  • For HTTP2, we can set the initial_stream_window_size to a large enough value.
  • Because this problem happens at response phase, we can also set the per_request_buffer_limit_bytes or request_body_buffer_limit to a large enough value to avoid this problem.
  • The fix will be released in the latest version.

Impact

DOS and crash

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVE ID

CVE-2025-62504

Weaknesses

No CWEs

Credits