CVE-2022-21657
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected products
4>= 1.20.0, < 1.20.2+ 2 more
- (no CPE)range: >= 1.20.0, < 1.20.2
- (no CPE)
- cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*range: <1.18.6
Patches
Vulnerability mechanics
References
2- github.com/envoyproxy/envoy/pull/630nvdPatchThird Party Advisory
- github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5gnvdIssue TrackingThird Party Advisory
News mentions
0No linked articles in our index yet.