Bug 2088738 (CVE-2022-29224) - CVE-2022-29224 envoy: Segfault in GrpcHealthCheckerImpl
Summary: CVE-2022-29224 envoy: Segfault in GrpcHealthCheckerImpl
Keywords:
Status: CLOSED ERRATA
Alias: CVE-2022-29224
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks: 2088743
TreeView+ depends on / blocked
 
Reported: 2022-05-20 11:38 UTC by Avinash Hanwate
Modified: 2022-06-13 16:50 UTC (History)
4 users (show)

Fixed In Version: Envoy 1.22.1, Envoy 1.21.3, Envoy 1.20.4, Envoy 1.19.5
Doc Type: If docs needed, set a value
Doc Text:
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.
Clone Of:
Environment:
Last Closed: 2022-06-13 16:50:16 UTC


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2022:5003 0 None None None 2022-06-13 11:55:05 UTC
Red Hat Product Errata RHSA-2022:5004 0 None None None 2022-06-13 12:33:42 UTC

Description Avinash Hanwate 2022-05-20 11:38:40 UTC
An attacker-controlled upstream server that is health checked using gRPC health checking can crash Envoy via a null pointer dereference in certain circumstances.

Comment 4 errata-xmlrpc 2022-06-13 11:55:03 UTC
This issue has been addressed in the following products:

  OpenShift Service Mesh 2.0

Via RHSA-2022:5003 https://access.redhat.com/errata/RHSA-2022:5003

Comment 5 errata-xmlrpc 2022-06-13 12:33:40 UTC
This issue has been addressed in the following products:

  OpenShift Service Mesh 2.1

Via RHSA-2022:5004 https://access.redhat.com/errata/RHSA-2022:5004

Comment 6 Product Security DevOps Team 2022-06-13 16:50:14 UTC
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):

https://access.redhat.com/security/cve/cve-2022-29224


Note You need to log in before you can comment on or make changes to this bug.