Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2022-23606

envoy: Stack exhaustion when a cluster is deleted via Cluster Discovery Service

Overview

Published
22 Feb 2022
Modified
17 Jun 2026
Medium CVE
1 Registry packages
11 OS packages
1 Linux distributions
Yes Fix available

Description

Envoy is an open source edge and service proxy, designed for cloud-native applications. When a cluster is deleted via Cluster Discovery Service (CDS) all idle connections established to endpoints in that cluster are disconnected. A recursion was introduced in the procedure of disconnecting idle connections that can lead to stack exhaustion and abnormal process termination when a cluster has a large number of idle connections. This infinite recursion causes Envoy to crash. Users are advised to upgrade.

Source: OX vulnerability database

Severity

6.5 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

Weakness: CWE-674

Affected packages · 1

Packages affected by CVE-2022-23606
EcosystemPackageVulnerableFixed in
Bitnami envoy >=1.20.0, <1.20.2>=1.21.0, <1.21.1 1.20.21.21.1

Open a package to see all its vulnerabilities.

Operating systems · 4 fixes

Red Hat 1 release · 3 packages

fixed 4
servicemesh servicemesh-prometheus kiali
Red Hat fixes for CVE-2022-23606
ReleasePackageFixed inAdvisory
8 servicemesh +6 0:2.0.9-3.el8 RHSA-2022:1276
8 servicemesh +5 0:2.1.2-4.el8 RHSA-2022:1275
8 servicemesh-prometheus 0:2.14.0-16.el8.1 RHSA-2022:1276
8 kiali 0:v1.24.7.redhat1-1.el8 RHSA-2022:1276

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.