RATATOSK
← All releases

Envoyv1.35.8

Security 2

Get Envoy alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Security2medium2

c-ares DNS use-after-free fixed

medium
AffectsEnvoy deployments using c-ares for DNS resolution

A non-FQDN ares_getaddrinfo query could crash Envoy when NXDOMAIN was followed by a failed search-domain retry and the resent query succeeded. Envoy v1.35.8 uses a patched c-ares version, fixing the use-after-free in this sequence.

Show release-note lines
  - c-ares/CVE-2025-0913:
      Use after free can crash Envoy due to malfunctioning or compromised DNS.
While a potentially severe bug in some cloud environments, this has limited exploitability
as any attacker would require control of DNS.
Envoy advisory is here https://github.com/envoyproxy/envoy/security/advisories/GHSA-fg9g-pvc4-776f
- dns : Update c-ares to version 1.34.6 to resolve CVE-2025-0913.
Use-after-free in c-ares can crash Envoy via compromised or malfunctioning DNS.
advisory: https://github.com/envoyproxy/envoy/security/advisories/GHSA-fg9g-pvc4-776f .
github.com/envoyproxy/envoy/releases/tag/v1.35.8

Envoy HTTP filter use-after-free after stream reset fixed

medium

2026-03-10 Security advisory GHSA-84xm-r438-86px published after the release

AffectsNot stated in the release notes

After a stream reset, a later DATA frame could make Envoy's HTTP filter manager call decodeData() on destroyed filters, causing a crash or memory corruption and potentially enabling remote code execution. It could also let data pass a stream termination and reach deeper filters or backend services after a security rejection; an unauthenticated remote client only needed to establish an HTTP/2 or HTTP/3 connection.

Show release-note lines
Security advisory
The `ActiveStream` object remains valid in memory during the deferred deletion window. If a `DATA` frame arrives on this stream immediately after the reset (e.g., in the same packet processing cycle), the HTTP/2 codec invokes `ActiveStream::decodeData`, which cascades to `FilterManager::decodeData`.
`FilterManager::decodeData` **fails to check the `saw_downstream_reset_` flag**. It iterates over the `decoder_filters_` list and invokes `decodeData()` on filters that have already received `onDestroy()`.
**Who can exploit this:**
Any remote attacker capable of establishing an HTTP/2 or HTTP/3 connection. No privileges/authentication required.
While the immediate symptom is a crash (DoS), the underlying primitive is a **Use-After-Free (CWE-416)**.
* **Exploitation:** By forcing `decodeData()` to execute on these now-freed objects, an attacker triggers undefined behavior. In a heap-groomed environment, an attacker could potentially replace the freed filter object with a malicious payload before the "Zombie" `decodeData` call occurs. This would allow for vtable hijacking or arbitrary write-what-where primitives, leading to **Remote Code Execution (RCE)**.
* **Scenario:** If a stream is reset due to a security violation (e.g., `StreamIdleTimeout`, `OverloadManager` rejection, or WAF triggering), this vulnerability allows the attacker to **bypass the termination**.
* **Result:** The attacker can force the processing of "Data" frames on a connection that the security policy explicitly attempted to close, allowing malicious payloads to reach deeper into the filter chain or backend services despite the rejection.
github.com/envoyproxy/envoy/security/advisories/GHSA-84xm-r438-86px
Security advisory
HTTP: filter chain execution on reset streams causing UAF crash
github.com/envoyproxy/envoy/security/advisories/GHSA-84xm-r438-86px

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.