Vulnerability Details : CVE-2022-21657
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.
Products affected by CVE-2022-21657
- cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*
- cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*
- cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2022-21657
0.05%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 17 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2022-21657
| Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
|---|---|---|---|---|---|---|
|
4.0
|
MEDIUM | AV:N/AC:L/Au:S/C:N/I:P/A:N |
8.0
|
2.9
|
NIST | |
|
6.5
|
MEDIUM | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N |
2.8
|
3.6
|
NIST | |
|
6.8
|
MEDIUM | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N |
1.6
|
5.2
|
GitHub, Inc. |
CWE ids for CVE-2022-21657
-
The product does not validate, or incorrectly validates, a certificate.Assigned by: security-advisories@github.com (Primary)
References for CVE-2022-21657
-
https://github.com/envoyproxy/envoy/pull/630
http: config options for adding custom request headers by rshriram · Pull Request #630 · envoyproxy/envoy · GitHubPatch;Third Party Advisory
-
https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g
X.509 Extended Key Usage and Trust Purposes bypass · Advisory · envoyproxy/envoy · GitHubIssue Tracking;Third Party Advisory
Jump to