LiveActive security incident?Get immediate response
CVE Record

CVE-2022-29224: Segmentation fault leading to crash in Envoy

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.

MediumCVSS 5.9Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This Envoy flaw can let a highly positioned attacker crash the proxy, causing service disruption. The attacker must control both an upstream host and the service discovery data for that host, so exposure is narrower than a typical internet-facing bug. The vendor fixed it in Envoy 1.22.1; disabling gRPC health checks is the stated workaround.

Executive priority

Treat as a targeted availability risk, not a broad compromise issue. Prioritize internet-facing or business-critical Envoy gateways where service discovery or upstream endpoints cross trust boundaries.

Technical view

Envoy versions before 1.22.1 can hit a null pointer dereference in GrpcHealthCheckerImpl. The crash condition involves gRPC upstream health checking plus retained service-discovery hosts. If the controlled host is removed from discovery and later fails gRPC health checking, Envoy may segfault. CVSS is 5.9 with high attack complexity.

Likely exposure

Most exposed environments are Envoy deployments before 1.22.1 using gRPC active health checks with service discovery such as DNS or EDS. Risk increases when upstream hosts or discovery inputs are controlled outside a trusted boundary.

Exploitation context

The source bundle does not report active exploitation, and CISA KEV status is false. Practical exploitation requires unusual control: both an upstream host and the service discovery path for that host.

Researcher notes

Evidence supports a denial-of-service condition only. The advisory describes a segmentation fault from CWE-476 in GrpcHealthCheckerImpl. No confidentiality or integrity impact is claimed, and no public exploitation is cited in the supplied sources.

Mitigation direction

  • Upgrade Envoy to version 1.22.1 or later.
  • If upgrading is delayed, disable gRPC health checking.
  • Replace gRPC health checks with another supported health check type.
  • Review vendor guidance before applying compensating controls.

Validation and detection

  • Inventory Envoy versions and flag any deployment before 1.22.1.
  • Identify clusters configured with gRPC upstream health checks.
  • Review service discovery sources for externally controlled upstream entries.
  • Confirm upgraded instances no longer run affected Envoy versions.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-476: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-29224 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.9 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.9CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H2.23.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.9Medium
CVSS 3.1 vector shape for CVE-2022-29224Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
envoyproxyenvoy< 1.22.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-476 · source CWE mapping

NULL Pointer Dereference

NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.