- Veröffentlicht
- 09.06.2022 16:00
- Zuletzt geändert
- 08.09.2026
- EPSS (30 Tage)
- 1.0 %
- CVSS-Vektor
- CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Beschreibung
Originaltext der Quelle, nicht übersetzt.
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.
Status beim Hersteller
Red Hat stuft seine Produktlinien ein: 2 behoben, 2 nicht betroffen.
Nicht betroffen (2)
OpenShift Service Mesh 2.0Nicht betroffenverwundbarer Code nicht enthaltenservicemesh, servicemesh-cni, servicemesh-operator, servicemesh-prometheus
OpenShift Service Mesh 2.1Nicht betroffenverwundbarer Code nicht enthaltenservicemesh, servicemesh-operator, servicemesh-prometheus, servicemesh-ratelimit
Betroffene Pakete im beobachteten Stack
Red Hat:service_mesh:2.0::el8servicemesh-proxy0:2.0.10-1.el8CVE-2022-29224
Red Hat:service_mesh:2.0::el8servicemesh-proxy0:2.0.10-1.el8RHSA-2022:5003 (über RHSA-2022:5003)
Red Hat:service_mesh:2.1::el8servicemesh0:2.1.3-1.el8RHSA-2022:5004 (über RHSA-2022:5004)
Red Hat:service_mesh:2.1::el8servicemesh-cni0:2.1.3-1.el8RHSA-2022:5004 (über RHSA-2022:5004)
Red Hat:service_mesh:2.1::el8servicemesh-operator0:2.1.3-2.el8RHSA-2022:5004 (über RHSA-2022:5004)
Red Hat:service_mesh:2.1::el8servicemesh-pilot-agent0:2.1.3-1.el8RHSA-2022:5004 (über RHSA-2022:5004)
Red Hat:service_mesh:2.1::el8servicemesh-pilot-discovery0:2.1.3-1.el8RHSA-2022:5004 (über RHSA-2022:5004)
Red Hat:service_mesh:2.1::el8servicemesh-prometheus0:2.23.0-7.el8RHSA-2022:5004 (über RHSA-2022:5004)
Red Hat:service_mesh:2.1::el8servicemesh-proxy0:2.1.3-1.el8CVE-2022-29224
Red Hat:service_mesh:2.1::el8servicemesh-proxy0:2.1.3-1.el8RHSA-2022:5004 (über RHSA-2022:5004)
Red Hat:service_mesh:2.1::el8servicemesh-proxy-debuginfo0:2.1.3-1.el8RHSA-2022:5004 (über RHSA-2022:5004)
Red Hat:service_mesh:2.1::el8servicemesh-proxy-debugsource0:2.1.3-1.el8RHSA-2022:5004 (über RHSA-2022:5004)
Red Hat:service_mesh:2.1::el8servicemesh-proxy-wasm0:2.1.3-1.el8RHSA-2022:5004 (über RHSA-2022:5004)
Red Hat:service_mesh:2.1::el8servicemesh-ratelimit0:2.1.3-1.el8RHSA-2022:5004 (über RHSA-2022:5004)
Weitere betroffene Pakete (3)
Bitnamienvoy1.22.1BIT-envoy-2022-29224
CVEenvoyproxy/envoykein Fix bekanntCVE-2022-29224
NVDenvoyproxy:envoy1.22.1CVE-2022-29224
Empfohlene Prüfung
- Feststellen, ob und in welcher Version die betroffenen Pakete in Ihren Systemen, Images und Abhängigkeiten vorkommen.
- Wo eine Fix-Version genannt ist: aktualisieren. Wo nicht: Hersteller-Advisory und Referenzen auf Workarounds prüfen.
- Erreichbarkeit beachten: Der Angriffsweg (Netzwerk · ohne Login) ist aus dem CVSS-Vektor abgeleitet.
Diese Seite sagt nichts darüber, ob Ihre Systeme betroffen sind. Das klärt erst eine Prüfung Ihrer Versionen.
Referenzen
- github.com/envoyproxy/envoy/security/advisories/GHSA-m4j9-86g3-8f49
- github.com/envoyproxy/envoy/commit/9b1c3962172a972bc0359398af6daa3790bb59db
- nvd.nist.gov/vuln/detail/CVE-2022-29224
- security.access.redhat.com/data/csaf/v2/vex/2022/cve-2022-29224.json
- access.redhat.com/security/cve/CVE-2022-29224
- bugzilla.redhat.com/show_bug.cgi
- www.cve.org/CVERecord