# Envoy v1.35.8

2025-12-10 · [릴리스 노트 원문](https://github.com/envoyproxy/envoy/releases/tag/v1.35.8) · [전체 정리](https://ratatosk.io/ko/releases/envoy/v1.35.8)

보안 2

## 보안 (2)

### [medium] c-ares DNS use-after-free 수정

- 영향 대상: DNS 해석에 c-ares를 사용하는 Envoy 배포
- [CVE-2025-0913](https://www.cve.org/CVERecord?id=CVE-2025-0913), [CVE-2025-62408](https://www.cve.org/CVERecord?id=CVE-2025-62408), [CVE-2025-67514](https://www.cve.org/CVERecord?id=CVE-2025-67514), [GHSA-fg9g-pvc4-776f](https://github.com/envoyproxy/envoy/security/advisories/GHSA-fg9g-pvc4-776f)

FQDN이 아닌 `ares_getaddrinfo` 질의에서 `NXDOMAIN` 응답을 받은 뒤 검색 도메인 재시도가 실패하고, 다시 전송한 질의가 성공하면 Envoy가 크래시할 수 있었습니다. Envoy v1.35.8은 패치된 c-ares 버전을 사용해 이 순서에서 발생하는 use-after-free를 수정합니다.

>   - 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 .

### [medium] Envoy HTTP 필터의 스트림 리셋 후 유스애프터프리 수정

- 2026-03-10 · [릴리스 뒤 보안 공지 GHSA-84xm-r438-86px 공개](https://github.com/envoyproxy/envoy/security/advisories/GHSA-84xm-r438-86px)
- 영향 대상: 릴리스 노트에 언급 없음
- [CVE-2026-26311](https://www.cve.org/CVERecord?id=CVE-2026-26311), [GHSA-84xm-r438-86px](https://github.com/envoyproxy/envoy/security/advisories/GHSA-84xm-r438-86px)

스트림이 리셋된 뒤 나중에 도착한 DATA 프레임 때문에 Envoy의 HTTP 필터 매니저가 이미 파괴된 필터에서 `decodeData()`를 호출할 수 있었습니다. 이로 인해 충돌이나 메모리 손상이 발생하고 원격 코드 실행으로 이어질 가능성도 있었습니다. 또한 보안 거부 뒤에도 데이터가 스트림 종료를 지나 더 깊은 필터나 백엔드 서비스에 도달할 수 있었습니다. 인증되지 않은 원격 클라이언트는 HTTP/2 또는 HTTP/3 연결만 수립하면 이 문제를 일으킬 수 있었습니다.

보안 공지:

> 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.

https://github.com/envoyproxy/envoy/security/advisories/GHSA-84xm-r438-86px

보안 공지:

> HTTP: filter chain execution on reset streams causing UAF crash

https://github.com/envoyproxy/envoy/security/advisories/GHSA-84xm-r438-86px

---

정리 내용은 AI가 작성하므로 틀릴 수 있으며, 보증 없이 제공합니다.
