CVE-2022-21657— X.509 Extended Key Usage and Trust Purposes bypass in Envoy
Quick assessment
Affected
envoyproxy envoy
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.
Envoy是一款开源的分布式代理服务器。 Envoy 存在信任管理问题漏洞，该漏洞源于Envoy 不会将它从对等方（作为 TLS 客户端或 TLS 服务器）接受的证书集限制为仅包含必要的扩展密钥使用（id-kp-serverAuth 和 id-kp-clientAuth，分别为 ）。 这意味着对等点可以提供电子邮件证书（例如 id-kp-emailProtection），作为叶证书或链中的 CA，并且将被 TLS 接受。 当与拉取请求 #630 中描述的问题结合使用时，这尤其糟糕，因为它允许仅用于 S/M
Possible ATT&CK Techniques 1 AI
T1557 · Adversary-in-the-Middle
Get alerts for future matching vulnerabilities
Log in to subscribe
I. Basic Information for CVE-2022-21657
Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗
Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.
Vulnerability Title
X.509 Extended Key Usage and Trust Purposes bypass in Envoy
Source: CVE Program / CVE List V5
Vulnerability Description
Envoy is an open source edge and service proxy, designed for cloud-native applications. In affected versions Envoy does not restrict the set of certificates it accepts from the peer, either as a TLS client or a TLS server, to only those certificates that contain the necessary extendedKeyUsage (id-kp-serverAuth and id-kp-clientAuth, respectively). This means that a peer may present an e-mail certificate (e.g. id-kp-emailProtection), either as a leaf certificate or as a CA in the chain, and it will be accepted for TLS. This is particularly bad when combined with the issue described in pull request #630, in that it allows a Web PKI CA that is intended only for use with S/MIME, and thus exempted from audit or supervision, to issue TLS certificates that will be accepted by Envoy. As a result Envoy will trust upstream certificates that should not be trusted. There are no known workarounds to this issue. Users are advised to upgrade.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
证书验证不恰当
Source: CVE Program / CVE List V5
Vulnerability Title
Envoy 信任管理问题漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
Envoy是一款开源的分布式代理服务器。 Envoy 存在信任管理问题漏洞，该漏洞源于Envoy 不会将它从对等方（作为 TLS 客户端或 TLS 服务器）接受的证书集限制为仅包含必要的扩展密钥使用（id-kp-serverAuth 和 id-kp-clientAuth，分别为 ）。 这意味着对等点可以提供电子邮件证书（例如 id-kp-emailProtection），作为叶证书或链中的 CA，并且将被 TLS 接受。 当与拉取请求 #630 中描述的问题结合使用时，这尤其糟糕，因为它允许仅用于 S/M
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)
Affected Products
| Vendor | Product | Affected Versions | CPE | Subscribe |
|---|---|---|---|---|
| envoyproxy | envoy | >= 1.20.0, < 1.20.2 | - |
|
II. Public POCs for CVE-2022-21657
| # | POC Description | Source Link | Shenlong Link |
|---|
AI-Generated POC
Premium
No public POC found.
Login to generate AI POCIII. Intelligence Information for CVE-2022-21657
请登录查看更多情报信息。
Patches & Fixes for CVE-2022-21657 (1)
-
https://github.com/envoyproxy/envoy/pull/630 x_refsource_MISC
Vendor Advisories for CVE-2022-21657 (1)
-
https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g x_refsource_CONFIRM
Same Patch Batch · envoyproxy · 2022-02-22 · 8 CVEs total
| CVE-2021-43826 | 7.5 HIGH | Crash when tunneling TCP over HTTP in Envoy |
| CVE-2022-21655 | 7.5 HIGH | Incorrect handling of internal redirects results in crash in Envoy |
| CVE-2021-43824 | 7.5 HIGH | Null pointer dereference in envoy |
| CVE-2022-21654 | 7.4 HIGH | Incorrect configuration handling allows TLS session re-use without re-validation in Envoy |
| CVE-2022-21656 | 7.4 HIGH | X.509 subjectAltName matching bypass in Envoy |
| CVE-2021-43825 | 6.1 MEDIUM | Use-after-free in Envoy |
| CVE-2022-23606 | 4.4 MEDIUM | Crash when a cluster is deleted in Envoy |
IV. Related Vulnerabilities
Same product: envoy
-
CVE-2026-73511
Envoy: Potential path-matching/authentication bypass when us -
CVE-2026-73553
Envoy: RBAC Authorization Bypass via Path Parameters -
CVE-2026-73551
Envoy: Path normalization does not handle dot and dotdot seg -
CVE-2026-73546
Envoy: Stored XSS in Admin Stats Interface (/stats?format=ht -
CVE-2026-73512
Envoy: use-after-free in QUIC on internal redirects
Same vendor: envoyproxy
-
CVE-2026-73511
Envoy: Potential path-matching/authentication bypass when us -
CVE-2026-73553
Envoy: RBAC Authorization Bypass via Path Parameters -
CVE-2026-73551
Envoy: Path normalization does not handle dot and dotdot seg -
CVE-2026-73546
Envoy: Stored XSS in Admin Stats Interface (/stats?format=ht -
CVE-2026-73512
Envoy: use-after-free in QUIC on internal redirects
Same weakness: CWE-295
-
CVE-2026-71885
MLS X.509 credential not bound to the LeafNode signature key -
CVE-2026-71889
PKIXCertPathReviewer does not apply X.509 name constraints t -
CVE-2026-85088
Apache Thrift, Apache Thrift: The C++ and D clients fall bac -
CVE-2026-85087
Apache Thrift: Python ≥3.12 host-name check silently becomes -
CVE-2026-85086
Apache Thrift: Perl TLS client disables certificate verifica
V. Comments for CVE-2022-21657
No comments yet