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-21656

envoy: X.509 subjectAltName matching (and nameConstraints) bypass

Overview

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

Description

Envoy is an open source edge and service proxy, designed for cloud-native applications. The default_validator.cc implementation used to implement the default certificate validation routines has a "type confusion" bug when processing subjectAltNames. This processing allows, for example, an rfc822Name or uniformResourceIndicator to be authenticated as a domain name. This confusion allows for the bypassing of nameConstraints, as processed by the underlying OpenSSL/BoringSSL implementation, exposing the possibility of impersonation of arbitrary servers. As a result Envoy will trust upstream certificates that should not be trusted.

Source: OX vulnerability database

Severity

5.9 · MEDIUM

CVSS 3.1 base score, scored by NVD.

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

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

Weakness: CWE-295, CWE-843

Affected packages · 1

Packages affected by CVE-2022-21656
EcosystemPackageVulnerableFixed in
Bitnami envoy <1.20.2 1.20.2

Open a package to see all its vulnerabilities.

Operating systems · 2 fixes

Red Hat 1 release · 1 package

affected 1 wont fix 1
servicemesh-proxy
Red Hat fixes for CVE-2022-21656
ReleasePackageFixed in
8 servicemesh-proxy affected
8 servicemesh-proxy +1 wont fix

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.