{"id":"CVE-2022-21657","aliases":["BIT-envoy-2022-21657","GHSA-837m-wjrv-vm5g"],"summary":"X.509 Extended Key Usage and Trust Purposes bypass in Envoy","published_at":"2022-02-22T22:30:12Z","modified_at":"2026-09-08T08:47:26.502676Z","products":[{"slug":"rhel","name":"Red Hat Enterprise Linux","category":"red-hat"}],"rating":{"severity":"medium","score":6.8,"vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","attack_path":"internet_authenticated","user_interaction":false,"malicious":false,"red_hat":"Moderate","vendor_ratings":[{"source":"Red Hat","rating":"Moderate"}]},"fix_available":false,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.0052200001664459705,"percentile":0.4504700005054474,"date":"2026-11-19T00:00:00Z"},"priority":7.8,"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.","affected_stack":[{"ecosystem":"Red Hat:service_mesh:2.0","package":"servicemesh-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"provider":"redhat-vex","source":"CVE-2022-21657","relation":"self"},{"ecosystem":"Red Hat:service_mesh:2.1","package":"servicemesh-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"provider":"redhat-vex","source":"CVE-2022-21657","relation":"self"},{"ecosystem":"Red Hat:service_mesh:2.1","package":"servicemesh-proxy-wasm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"provider":"redhat-vex","source":"CVE-2022-21657","relation":"self"}],"affected_other":[{"ecosystem":"Bitnami","package":"envoy","purl":"pkg:bitnami/envoy","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.18.6"},{"introduced":"1.19.0"},{"fixed":"1.19.3"},{"introduced":"1.20.0"},{"fixed":"1.20.2"}]}],"fixed":["1.18.6","1.19.3","1.20.2"],"provider":"osv","source":"BIT-envoy-2022-21657","relation":"self"},{"ecosystem":"CVE","package":"envoyproxy/envoy","versions":[">= 1.20.0, < 1.20.2",">= 1.19.0, < 1.19.3","< 1.18.6"],"provider":"cvelistv5","source":"CVE-2022-21657","relation":"self"},{"ecosystem":"NVD","package":"envoyproxy:envoy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.18.6"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.19.0"},{"fixed":"1.19.3"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.20.0"},{"fixed":"1.20.2"}]}],"fixed":["1.18.6","1.19.3","1.20.2"],"provider":"nvd","source":"CVE-2022-21657","relation":"self"}],"product_status":[{"vendor":"Red Hat","product":"OpenShift Service Mesh 2","cpe":"cpe:/a:redhat:service_mesh:2","status":"not_affected","packages":["openshift-service-mesh/proxyv2-rhel8"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2022-21657"},{"vendor":"Red Hat","product":"OpenShift Service Mesh 2.0","cpe":"cpe:/a:redhat:service_mesh:2.0","status":"affected","packages":["servicemesh-proxy"],"package_count":1,"fixed":[],"advisories":[],"note":"Affected","provider":"redhat-vex","source":"CVE-2022-21657"},{"vendor":"Red Hat","product":"OpenShift Service Mesh 2.1","cpe":"cpe:/a:redhat:service_mesh:2.1","status":"affected","packages":["servicemesh-proxy","servicemesh-proxy-wasm"],"package_count":2,"fixed":[],"advisories":[],"note":"Will not fix","provider":"redhat-vex","source":"CVE-2022-21657"}],"records":[{"provider":"cvelistv5","source_id":"CVE-2022-21657","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2022-21657","license":"CC-BY-4.0","published_at":"2022-02-22T22:30:12Z","modified_at":"2025-04-23T19:01:32.824Z","summary":"X.509 Extended Key Usage and Trust Purposes bypass in Envoy","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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","source":"CVE-2022-21657"}],"affected":[{"ecosystem":"CVE","package":"envoyproxy/envoy","versions":[">= 1.20.0, < 1.20.2",">= 1.19.0, < 1.19.3","< 1.18.6"],"provider":"cvelistv5","source":"CVE-2022-21657","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g"},{"type":"WEB","url":"https://github.com/envoyproxy/envoy/pull/630"}]},{"provider":"nvd","source_id":"CVE-2022-21657","relation":"self","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-21657","severity":[],"affected":[{"ecosystem":"NVD","package":"envoyproxy:envoy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.18.6"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.19.0"},{"fixed":"1.19.3"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.20.0"},{"fixed":"1.20.2"}]}],"fixed":["1.18.6","1.19.3","1.20.2"],"provider":"nvd","source":"CVE-2022-21657","relation":"self"}],"product_status":[],"references":[]},{"provider":"osv","source_id":"BIT-envoy-2022-21657","relation":"self","url":"https://osv.dev/vulnerability/BIT-envoy-2022-21657","license":"Apache-2.0","published_at":"2024-03-06T10:55:54.594Z","modified_at":"2026-09-08T08:47:26.502676Z","summary":"X.509 Extended Key Usage and Trust Purposes bypass in Envoy","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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","source":"BIT-envoy-2022-21657"}],"affected":[{"ecosystem":"Bitnami","package":"envoy","purl":"pkg:bitnami/envoy","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.18.6"},{"introduced":"1.19.0"},{"fixed":"1.19.3"},{"introduced":"1.20.0"},{"fixed":"1.20.2"}]}],"fixed":["1.18.6","1.19.3","1.20.2"],"provider":"osv","source":"BIT-envoy-2022-21657","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://github.com/envoyproxy/envoy/pull/630"},{"type":"ADVISORY","url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-21657"}]},{"provider":"redhat-vex","source_id":"CVE-2022-21657","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2022-21657","license":"CC-BY-4.0","published_at":"2022-02-23T00:00:00Z","modified_at":"2023-09-01T03:02:25Z","summary":"envoy: X.509 Extended Key Usage and Trust Purposes bypass","details":"A flaw was found in envoy. This issue occurs when it does not restrict the set of certificates it accepts from the peer, either as a TLS client or a TLS server, and only to those certificates that contain the necessary extendedKeyUsage (id-kp-serverAuth and id-kp-clientAuth, respectively).","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","source":"CVE-2022-21657"},{"type":"Red Hat","score":"Moderate","source":"CVE-2022-21657"}],"affected":[{"ecosystem":"Red Hat:service_mesh:2.0","package":"servicemesh-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"provider":"redhat-vex","source":"CVE-2022-21657","relation":"self"},{"ecosystem":"Red Hat:service_mesh:2.1","package":"servicemesh-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"provider":"redhat-vex","source":"CVE-2022-21657","relation":"self"},{"ecosystem":"Red Hat:service_mesh:2.1","package":"servicemesh-proxy-wasm","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"provider":"redhat-vex","source":"CVE-2022-21657","relation":"self"}],"product_status":[{"vendor":"Red Hat","product":"OpenShift Service Mesh 2","cpe":"cpe:/a:redhat:service_mesh:2","status":"not_affected","packages":["openshift-service-mesh/proxyv2-rhel8"],"package_count":1,"fixed":[],"advisories":[],"note":"vulnerable_code_not_present","provider":"redhat-vex","source":"CVE-2022-21657"},{"vendor":"Red Hat","product":"OpenShift Service Mesh 2.0","cpe":"cpe:/a:redhat:service_mesh:2.0","status":"affected","packages":["servicemesh-proxy"],"package_count":1,"fixed":[],"advisories":[],"note":"Affected","provider":"redhat-vex","source":"CVE-2022-21657"},{"vendor":"Red Hat","product":"OpenShift Service Mesh 2.1","cpe":"cpe:/a:redhat:service_mesh:2.1","status":"affected","packages":["servicemesh-proxy","servicemesh-proxy-wasm"],"package_count":2,"fixed":[],"advisories":[],"note":"Will not fix","provider":"redhat-vex","source":"CVE-2022-21657"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2022/cve-2022-21657.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2022-21657"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2057272"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2022-21657"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-21657"},{"type":"WEB","url":"https://github.com/envoyproxy/envoy/pull/630"},{"type":"WEB","url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g"}]}],"references":[{"type":"WEB","url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g"},{"type":"WEB","url":"https://github.com/envoyproxy/envoy/pull/630"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-21657"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2022/cve-2022-21657.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2022-21657"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2057272"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2022-21657"}],"sources":[{"provider":"cvelistv5","source_id":"CVE-2022-21657","url":"https://www.cve.org/CVERecord?id=CVE-2022-21657","license":"CC-BY-4.0","modified_at":"2025-04-23T19:01:32.824Z","relation":"self"},{"provider":"nvd","source_id":"CVE-2022-21657","url":"https://nvd.nist.gov/vuln/detail/CVE-2022-21657","relation":"self"},{"provider":"osv","source_id":"BIT-envoy-2022-21657","url":"https://osv.dev/vulnerability/BIT-envoy-2022-21657","license":"Apache-2.0","modified_at":"2026-09-08T08:47:26.502676Z","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2022-21657","url":"https://access.redhat.com/security/cve/CVE-2022-21657","license":"CC-BY-4.0","modified_at":"2023-09-01T03:02:25Z","relation":"self"}]}
