CVE-2022-29224 json
Segmentation fault leading to crash in Envoy
published 2022-06-09 4 y ago modified 2026-09-08 2 mo ago also BIT-envoy-2022-29224 , EUVD-2022-33586 , GHSA-m4j9-86g3-8f49
- cvss
- 5.9
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 64%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- bitnami envoy 1.22.1
- envoyproxy envoy 1.22.1
- servicemesh service mesh 2.1 2.1.3-1.el8
- servicemesh-cni service mesh 2.1 2.1.3-1.el8
- servicemesh-proxy service mesh 2.1 2.1.3-1.el8
- servicemesh-operator service mesh 2.1 2.1.3-2.el8
- servicemesh-ratelimit service mesh 2.1 2.1.3-1.el8
- servicemesh-prometheus service mesh 2.1 2.23.0-7.el8
- servicemesh-proxy-wasm service mesh 2.1 2.1.3-1.el8
- servicemesh-pilot-agent service mesh 2.1 2.1.3-1.el8
red hat advisories RHSA-2022:5004RHSA-2022:5003
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2022-29224 updated cvss 5.9
envoy: Segfault in GrpcHealthCheckerImpl
-
Red Hat OpenShift Service Mesh 2.0 servicemesh-proxy 2.0.10-1.el8fixed: vendor fix “Disable gRPC health checking and/or replace it with a different health checking type.” RHSA-2022:5003
-
Red Hat OpenShift Service Mesh 2.1 servicemesh-proxy 2.1.3-1.el8, servicemesh-proxy-wasm 2.1.3-1.el8fixed: vendor fix “Disable gRPC health checking and/or replace it with a different health checking type.” RHSA-2022:5004
-
Red Hat OpenShift Service Mesh 2.0 servicemesh 2.0.10-1.el8, servicemesh-cni 2.0.10-1.el8, servicemesh-mixc 2.0.10-1.el8, servicemesh-mixs 2.0.10-1.el8, servicemesh-istioctl 2.0.10-1.el8, servicemesh-operator 2.0.10-1.el8, +3 more Red Hat OpenShift Service Mesh 2.1 servicemesh 2.1.3-1.el8, servicemesh-cni 2.1.3-1.el8, servicemesh-operator 2.1.3-2.el8, servicemesh-ratelimit 2.1.3-1.el8, servicemesh-pilot-agent 2.1.3-1.el8, servicemesh-prometheus 2.23.0-7.el8, +1 morenot affected: vulnerable code not present “Disable gRPC health checking and/or replace it with a different health checking type.”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 18 mo ago
Exploit prediction
1.04% chance of exploitation in the next 30 days, higher than 64% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:N/A:P |
| OSV | 3.1 | 5.9 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | envoy | <1.22.1 |
1.22.1 |
Affected products
- envoyproxy envoy
Classification
- Weakness
-
- CWE-476 NULL Pointer Dereference
References
Sources
- CVE List CVE-2022-29224
- NVD CVE-2022-29224
- OSV BIT-envoy-2022-29224
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.