{"id":"CVE-2020-15104","state":"PUBLISHED","title":"TLS Validation Vulnerability in Envoy","description":"In Envoy before versions 1.12.6, 1.13.4, 1.14.4, and 1.15.0 when validating TLS certificates, Envoy would incorrectly allow a wildcard DNS Subject Alternative Name apply to multiple subdomains. For example, with a SAN of *.example.com, Envoy would incorrectly allow nested.subdomain.example.com, when it should only allow subdomain.example.com. This defect applies to both validating a client TLS certificate in mTLS, and validating a server TLS certificate for upstream connections. This vulnerability is only applicable to situations where an untrusted entity can obtain a signed wildcard TLS certificate for a domain of which you only intend to trust a subdomain of. For example, if you intend to trust api.mysubdomain.example.com, and an untrusted actor can obtain a signed TLS certificate for *.example.com or *.com. Configurations are vulnerable if they use verify_subject_alt_name in any Envoy version, or if they use match_subject_alt_names in version 1.14 or later. This issue has been fixed in Envoy versions 1.12.6, 1.13.4, 1.14.4, 1.15.0.","publishedAt":"2020-07-14T22:05:14.000Z","updatedAt":"2024-08-04T13:08:22.235Z","severity":{"score":4.6,"label":"Medium","version":"3.1","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","source":"GitHub_M"},"assigner":"GitHub_M","products":["envoyproxy envoy"],"affected":[{"vendor":"envoyproxy","product":"envoy","versions":[{"version":"< 1.12.6","status":"affected"},{"version":">= 1.13.0, < 1.13.4","status":"affected"},{"version":">= 1.14.0, < 1.14.4","status":"affected"}]}],"references":["https://github.com/envoyproxy/envoy/security/advisories/GHSA-w5f5-6qhq-hhrg"],"weaknesses":["CWE-346"],"ingestedAt":"2026-10-29T19:46:36.523Z","source":{"repository":"CVEProject/cvelistV5","path":"cves/2020/15xxx/CVE-2020-15104.json","commit":"556c9d3a8cd17e218bb8e452ba7cd619a384ff47"},"raw":{"dataType":"CVE_RECORD","dataVersion":"5.1","cveMetadata":{"cveId":"CVE-2020-15104","state":"PUBLISHED","datePublished":"2020-07-14T22:05:14.000Z","dateUpdated":"2024-08-04T13:08:22.235Z","assignerShortName":"GitHub_M","assignerOrgId":"a0819718-46f1-4df5-94e2-005712e83aaa","dateReserved":"2020-06-25T00:00:00.000Z"},"containers":{"cna":{"title":"TLS Validation Vulnerability in Envoy","descriptions":[{"lang":"en","value":"In Envoy before versions 1.12.6, 1.13.4, 1.14.4, and 1.15.0 when validating TLS certificates, Envoy would incorrectly allow a wildcard DNS Subject Alternative Name apply to multiple subdomains. For example, with a SAN of *.example.com, Envoy would incorrectly allow nested.subdomain.example.com, when it should only allow subdomain.example.com. This defect applies to both validating a client TLS certificate in mTLS, and validating a server TLS certificate for upstream connections. This vulnerability is only applicable to situations where an untrusted entity can obtain a signed wildcard TLS certificate for a domain of which you only intend to trust a subdomain of. For example, if you intend to trust api.mysubdomain.example.com, and an untrusted actor can obtain a signed TLS certificate for *.example.com or *.com. Configurations are vulnerable if they use verify_subject_alt_name in any Envoy version, or if they use match_subject_alt_names in version 1.14 or later. This issue has been fixed in Envoy versions 1.12.6, 1.13.4, 1.14.4, 1.15.0."}],"affected":[{"vendor":"envoyproxy","product":"envoy","versions":[{"version":"< 1.12.6","status":"affected"},{"version":">= 1.13.0, < 1.13.4","status":"affected"},{"version":">= 1.14.0, < 1.14.4","status":"affected"}]}],"references":[{"url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-w5f5-6qhq-hhrg","tags":["x_refsource_CONFIRM"]}],"metrics":[{"cvssV3_1":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":4.6,"baseSeverity":"MEDIUM","confidentialityImpact":"LOW","integrityImpact":"LOW","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"REQUIRED","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"}}],"problemTypes":[{"descriptions":[{"cweId":"CWE-346","description":"CWE-346: Origin Validation Error","lang":"en","type":"CWE"}]}],"providerMetadata":{"shortName":"GitHub_M","dateUpdated":"2020-07-14T22:05:14.000Z","orgId":"a0819718-46f1-4df5-94e2-005712e83aaa"},"source":{"advisory":"GHSA-w5f5-6qhq-hhrg","discovery":"UNKNOWN"},"x_legacyV4Record":{"CVE_data_meta":{"ASSIGNER":"security-advisories@github.com","ID":"CVE-2020-15104","STATE":"PUBLIC","TITLE":"TLS Validation Vulnerability in Envoy"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"envoy","version":{"version_data":[{"version_value":"< 1.12.6"},{"version_value":">= 1.13.0, < 1.13.4"},{"version_value":">= 1.14.0, < 1.14.4"}]}}]},"vendor_name":"envoyproxy"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"In Envoy before versions 1.12.6, 1.13.4, 1.14.4, and 1.15.0 when validating TLS certificates, Envoy would incorrectly allow a wildcard DNS Subject Alternative Name apply to multiple subdomains. For example, with a SAN of *.example.com, Envoy would incorrectly allow nested.subdomain.example.com, when it should only allow subdomain.example.com. This defect applies to both validating a client TLS certificate in mTLS, and validating a server TLS certificate for upstream connections. This vulnerability is only applicable to situations where an untrusted entity can obtain a signed wildcard TLS certificate for a domain of which you only intend to trust a subdomain of. For example, if you intend to trust api.mysubdomain.example.com, and an untrusted actor can obtain a signed TLS certificate for *.example.com or *.com. Configurations are vulnerable if they use verify_subject_alt_name in any Envoy version, or if they use match_subject_alt_names in version 1.14 or later. This issue has been fixed in Envoy versions 1.12.6, 1.13.4, 1.14.4, 1.15.0."}]},"impact":{"cvss":{"attackComplexity":"LOW","attackVector":"NETWORK","availabilityImpact":"NONE","baseScore":4.6,"baseSeverity":"MEDIUM","confidentialityImpact":"LOW","integrityImpact":"LOW","privilegesRequired":"LOW","scope":"UNCHANGED","userInteraction":"REQUIRED","vectorString":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","version":"3.1"}},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"CWE-346: Origin Validation Error"}]}]},"references":{"reference_data":[{"name":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-w5f5-6qhq-hhrg","refsource":"CONFIRM","url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-w5f5-6qhq-hhrg"}]},"source":{"advisory":"GHSA-w5f5-6qhq-hhrg","discovery":"UNKNOWN"}}},"adp":[{"title":"CVE Program Container","references":[{"url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-w5f5-6qhq-hhrg","tags":["x_refsource_CONFIRM","x_transferred"]}],"providerMetadata":{"shortName":"CVE","orgId":"af854a3a-2127-422b-91ae-364da2661108","dateUpdated":"2024-08-04T13:08:22.235Z"}}]}}}