CVE-2022-29224

mediumpriority · track · 24EPSS 0.010 · 63 %ileDEEUUS
grimoire priorityP3 · Track
Exploitable?
—
no known exploitation
Likely / severe?
1.02% (63rd) EPSS
CVSS 4.3 · medium
Is it mine?
66 products
Check your exposure
Who says so?
5 sources
cnnvd · enisa_euvd · osv · cert_bund

EPSS · scored 2026-10-27

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.

01

remediations

Vendor fix, mitigation, or workaround guidance, as published by each source.

A vendor fix is available.

  • Fixedservicemesh-proxy-0:2.0.10-1.el8.ppc64le as a component of OpenShift Service Mesh 2.0redhat_csaf

    The OpenShift Service Mesh release notes provide information on the features and known issues: https://docs.openshift.com/container-platform/latest/service_mesh/v2x/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2022:5003
  • Fixedservicemesh-proxy-0:2.0.10-1.el8.s390x as a component of OpenShift Service Mesh 2.0redhat_csaf

    The OpenShift Service Mesh release notes provide information on the features and known issues: https://docs.openshift.com/container-platform/latest/service_mesh/v2x/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2022:5003
  • Fixedservicemesh-proxy-0:2.0.10-1.el8.src as a component of OpenShift Service Mesh 2.0redhat_csaf

    The OpenShift Service Mesh release notes provide information on the features and known issues: https://docs.openshift.com/container-platform/latest/service_mesh/v2x/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2022:5003
  • Fixedservicemesh-proxy-0:2.0.10-1.el8.x86_64 as a component of OpenShift Service Mesh 2.0redhat_csaf

    The OpenShift Service Mesh release notes provide information on the features and known issues: https://docs.openshift.com/container-platform/latest/service_mesh/v2x/servicemesh-release-notes.html

    https://access.redhat.com/errata/RHSA-2022:5003
  • Workaroundservicemesh-0:2.0.10-1.el8.ppc64le as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-0:2.0.10-1.el8.s390x as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-0:2.0.10-1.el8.src as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-0:2.0.10-1.el8.x86_64 as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-cni-0:2.0.10-1.el8.ppc64le as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-cni-0:2.0.10-1.el8.s390x as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-cni-0:2.0.10-1.el8.src as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-cni-0:2.0.10-1.el8.x86_64 as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-istioctl-0:2.0.10-1.el8.ppc64le as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-istioctl-0:2.0.10-1.el8.s390x as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-istioctl-0:2.0.10-1.el8.x86_64 as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-mixc-0:2.0.10-1.el8.ppc64le as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-mixc-0:2.0.10-1.el8.s390x as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-mixc-0:2.0.10-1.el8.x86_64 as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-mixs-0:2.0.10-1.el8.ppc64le as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-mixs-0:2.0.10-1.el8.s390x as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-mixs-0:2.0.10-1.el8.x86_64 as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-operator-0:2.0.10-1.el8.ppc64le as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-operator-0:2.0.10-1.el8.s390x as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-operator-0:2.0.10-1.el8.src as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-operator-0:2.0.10-1.el8.x86_64 as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-pilot-agent-0:2.0.10-1.el8.ppc64le as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-pilot-agent-0:2.0.10-1.el8.s390x as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-pilot-agent-0:2.0.10-1.el8.x86_64 as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-pilot-discovery-0:2.0.10-1.el8.ppc64le as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-pilot-discovery-0:2.0.10-1.el8.s390x as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-pilot-discovery-0:2.0.10-1.el8.x86_64 as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-prometheus-0:2.14.0-17.el8.1.ppc64le as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-prometheus-0:2.14.0-17.el8.1.s390x as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-prometheus-0:2.14.0-17.el8.1.src as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-prometheus-0:2.14.0-17.el8.1.x86_64 as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-proxy-0:2.0.10-1.el8.ppc64le as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-proxy-0:2.0.10-1.el8.s390x as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-proxy-0:2.0.10-1.el8.src as a component of OpenShift Service Mesh 2.0redhat_csaf

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

  • Workaroundservicemesh-proxy-0:2.0.10-1.el8.x86_64 as a component of OpenShift Service Mesh 2.0redhat_csaf

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

02

cvss

Technical severity, 0–10. One row per scoring source.

5.9
010

base score 0–10 · higher = more severe · hover a vector to decode

v2.04.3mediumAV:N/AC:M/Au:N/C:N/I:N/A:Pprimary · NVD / NIST USexploitability 8.6 · impact 2.9
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:Hprimary · NVD / NIST USexploitability 2.2 · impact 3.6
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondary · ENISA EU
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondary · security-advisories@github.comexploitability 2.2 · impact 3.6
v3.15.4mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H/E:Usecondary · CVSS-BT (t0sche)
v3.15.9mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:Hsecondary · Red Hat Product Security US
03

ssvc

A stakeholder decision — act, attend, or track — from exploitation and impact.

Trackcoordinatorcisa_ssvcUS
04

weaknesses

The CWE weakness classes this flaw belongs to.

05

affected products (66)

Products and version ranges known to be affected.

06

advisories (3)

Vendor and ecosystem advisories describing this.

  • RHSA-2022:5003Red Hat Security Advisory: Red Hat OpenShift Service Mesh 2.0.10 security update2022-06-13csaf · redhat_csafUS

    An update is now available for Red Hat OpenShift Service Mesh 2.0.10. Red Hat Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating, is available for each vulnerability from the CVE link(s) in the References section.

  • WID-SEC-W-2022-0288Red Hat OpenShift: Mehrere SchwachstellenDeutsch2022-06-13csaf · cert_bundDE

    Ein entfernter, anonymer Angreifer kann mehrere Schwachstellen in Red Hat OpenShift ausnutzen, um einen Denial of Service Angriff durchzuführen, einen nicht näher spezifizierten Angriff durchzuführen, vertrauliche Informationen offenzulegen und Daten zu manipulieren.

  • BIT-envoy-2022-29224Segmentation fault leading to crash in Envoy2024-03-06vendor · osvUS

    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.

07

also known as (3)

Other names and identifiers for this entity.

08

sources

Which sources assert this record, and when.

09

references (14)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan