{"api_version":"1","generated_at":"2026-04-23T02:37:47+00:00","cve":"CVE-2022-21657","urls":{"html":"https://cve.report/CVE-2022-21657","api":"https://cve.report/api/cve/CVE-2022-21657.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2022-21657","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2022-21657"},"summary":{"title":"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.","state":"PUBLIC","assigner":"security-advisories@github.com","published_at":"2022-02-22 23:15:00","updated_at":"2022-03-07 15:25:00"},"problem_types":["CWE-295"],"metrics":[],"references":[{"url":"https://github.com/envoyproxy/envoy/pull/630","name":"https://github.com/envoyproxy/envoy/pull/630","refsource":"MISC","tags":[],"title":"http: config options for adding custom request headers by rshriram · Pull Request #630 · envoyproxy/envoy · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g","name":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g","refsource":"CONFIRM","tags":[],"title":"X.509 Extended Key Usage and Trust Purposes bypass · Advisory · envoyproxy/envoy · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"404"},{"url":"https://www.cve.org/CVERecord?id=CVE-2022-21657","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2022-21657","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2022","cve_id":"21657","vulnerable":"1","versionEndIncluding":"","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"envoyproxy","cpe5":"envoy","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"}],"vendor_comments":[],"enrichments":{"kev":null,"epss":null,"legacy_qids":[]},"source_records":{"cve_program":{"CVE_data_meta":{"ASSIGNER":"security-advisories@github.com","ID":"CVE-2022-21657","STATE":"PUBLIC","TITLE":"X.509 Extended Key Usage and Trust Purposes bypass in Envoy"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"envoy","version":{"version_data":[{"version_value":">= 1.20.0, < 1.20.2"},{"version_value":">= 1.19.0, < 1.19.3"},{"version_value":"< 1.18.6"}]}}]},"vendor_name":"envoyproxy"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"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."}]},"impact":{"cvss":{"attackComplexity":"HIGH","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":6.8,"baseSeverity":"MEDIUM","confidentialityImpact":"HIGH","integrityImpact":"HIGH","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"NONE","vectorString":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-295: Improper Certificate Validation"}]}]},"references":{"reference_data":[{"name":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g","refsource":"CONFIRM","url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g"},{"name":"https://github.com/envoyproxy/envoy/pull/630","refsource":"MISC","url":"https://github.com/envoyproxy/envoy/pull/630"}]},"source":{"advisory":"GHSA-837m-wjrv-vm5g","discovery":"UNKNOWN"}},"nvd":{"publishedDate":"2022-02-22 23:15:00","lastModifiedDate":"2022-03-07 15:25:00","problem_types":["CWE-295"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N","attackVector":"NETWORK","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"NONE","integrityImpact":"HIGH","availabilityImpact":"NONE","baseScore":6.5,"baseSeverity":"MEDIUM"},"exploitabilityScore":2.8,"impactScore":3.6},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:L/Au:S/C:N/I:P/A:N","accessVector":"NETWORK","accessComplexity":"LOW","authentication":"SINGLE","confidentialityImpact":"NONE","integrityImpact":"PARTIAL","availabilityImpact":"NONE","baseScore":4},"severity":"MEDIUM","exploitabilityScore":8,"impactScore":2.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":false}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*","versionStartIncluding":"1.20.0","versionEndExcluding":"1.20.2","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*","versionStartIncluding":"1.19.0","versionEndExcluding":"1.19.3","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*","versionEndExcluding":"1.18.6","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2022","CveId":"21657","Ordinal":"221459","Title":"CVE-2022-21657","CVE":"CVE-2022-21657","Year":"2022"},"notes":[{"CveYear":"2022","CveId":"21657","Ordinal":"1","NoteData":"** RESERVED ** This candidate has been reserved by an organization or individual that will use it when announcing a new security problem. When the candidate has been publicized, the details for this candidate will be provided.","Type":"Description","Title":null}]}}}