-
Notifications
You must be signed in to change notification settings - Fork 61
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
x/vulndb: potential Go vuln in github.com/envoyproxy/envoy: CVE-2022-29224 #484
Labels
excluded: NOT_GO_CODE
This vulnerability does not refer to a Go module.
Comments
neild
added
excluded: NOT_GO_CODE
This vulnerability does not refer to a Go module.
and removed
NotGoVuln
labels
Aug 10, 2022
This was referenced Apr 4, 2023
This was referenced Jul 13, 2023
This was referenced Jul 25, 2023
This was referenced Nov 8, 2023
This was referenced Nov 8, 2023
This was referenced Feb 10, 2024
This was referenced Apr 10, 2024
This was referenced Jun 7, 2024
This was referenced Sep 20, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
CVE-2022-29224 references github.com/envoyproxy/envoy, which may be a Go module.
Description:
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.
Links:
See doc/triage.md for instructions on how to triage this report.
The text was updated successfully, but these errors were encountered: