First published: Fri May 20 2022(Updated: )
Envoy is a cloud-native high-performance proxy. Versions of envoy prior to 1.22.1 are subject to a segmentation fault in the GrpcHealthCheckerImpl. Envoy can perform various types of upstream health checking. One of them uses gRPC. Envoy also has a feature which can “hold� (prevent removal) upstream hosts obtained via service discovery until configured active health checking fails. If an attacker controls an upstream host and also controls service discovery of that host (via DNS, the EDS API, etc.), an attacker can crash Envoy by forcing removal of the host from service discovery, and then failing the gRPC health check request. This will crash Envoy via a null pointer dereference. Users are advised to upgrade to resolve this vulnerability. Users unable to upgrade may disable gRPC health checking and/or replace it with a different health checking type as a mitigation.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Envoyproxy Envoy | <1.22.1 | |
redhat/servicemesh-proxy | <0:2.0.10-1.el8 | 0:2.0.10-1.el8 |
redhat/servicemesh-proxy | <0:2.1.3-1.el8 | 0:2.1.3-1.el8 |
Disable gRPC health checking and/or replace it with a different health checking type.
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-29224 is a vulnerability in Envoy that allows an attacker to cause a segmentation fault in the GrpcHealthCheckerImpl.
CVE-2022-29224 has a severity value of 5.9, which is considered medium.
Versions of Envoy prior to 1.22.1 are affected by CVE-2022-29224.
To fix CVE-2022-29224, update Envoy to version 1.22.1 or later.
The CWE ID for CVE-2022-29224 is 476.