CVE-2022-21657: Envoy is an open source edge and service proxy, designed for cloud-native applications.
Medium CVSS 6.5
- CVE id
- CVE-2022-21657
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| Envoy Runtimes and servers |
< 1.18.6 >= 1.19.0, < 1.19.3 >= 1.20.0, < 1.20.2 |
1.18.6, 1.19.3, 1.20.2 |
How to fix it
Upgrade Envoy to the fixed release of the line you run: 1.18.6, 1.19.3, 1.20.2.
envoy --version
- Upgrade Envoy (the envoyproxy/envoy image tag) to the patched release.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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.
References
- CVE-2022-21657 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2022-21657
- Web: https://github.com/envoyproxy/envoy/pull/630
- Web: https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g
- Web: https://github.com/envoyproxy/envoy/pull/630
- Web: https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.