CVE-2022-29224: Segmentation fault leading to crash in Envoy

Published May 20, 2022
·
Updated

A flaw was found in Envoy. This flaw allows an attacker who controls an upstream host and also controls service discovery of that host (via DNS, the EDS API, etc.) to crash Envoy by forcing the removal of the host from service discovery and then failing the gRPC health check request. This issue crashes Envoy via a NULL pointer dereference.

Other sources

An attacker-controlled upstream server that is health checked using gRPC health checking can crash Envoy via a null pointer dereference in certain circumstances.

Red Hat

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.

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.

Affected Software

7 affected componentsFixes available
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
redhat/Envoy<1.22.1
1.22.1
redhat/Envoy<1.21.3
1.21.3
redhat/Envoy<1.20.4
1.20.4
redhat/Envoy<1.19.5
1.19.5
Envoyproxy Envoy<1.22.1

Remediation

Information

Disable gRPC health checking and/or replace it with a different health checking type.

Event History

Jun 9, 2022
CVE Published
02:00 PM
CVE Published
via MITRE·07:10 PM
Data Sourced
via MITRE·07:10 PM
DescriptionSeverityWeakness

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is CVE-2022-29224?

CVE-2022-29224 is a vulnerability in Envoy that allows an attacker to cause a segmentation fault in the GrpcHealthCheckerImpl.

2

What is the severity of CVE-2022-29224?

CVE-2022-29224 has a severity value of 5.9, which is considered medium.

3

What software versions are affected by CVE-2022-29224?

Versions of Envoy prior to 1.22.1 are affected by CVE-2022-29224.

4

How can I fix CVE-2022-29224?

To fix CVE-2022-29224, update Envoy to version 1.22.1 or later.

5

What is the Common Weakness Enumeration (CWE) ID for CVE-2022-29224?

The CWE ID for CVE-2022-29224 is 476.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203