{"id":"CVE-2020-15104","aliases":["BIT-envoy-2020-15104","GHSA-w5f5-6qhq-hhrg","RHSA-2020:3090"],"summary":"TLS Validation Vulnerability in Envoy","published_at":"2020-07-08T00:00:00Z","modified_at":"2026-09-08T08:47:07.47094Z","products":[{"slug":"rhel","name":"Red Hat Enterprise Linux","category":"red-hat"}],"rating":{"severity":"medium","score":6.6,"vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N","attack_path":"internet_authenticated","user_interaction":false,"malicious":false,"red_hat":"Moderate","vendor_ratings":[{"source":"Red Hat","rating":"Moderate"}]},"fix_available":true,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.002520000096410513,"percentile":0.16847999393939972,"date":"2026-11-19T00:00:00Z"},"priority":7.6,"details":"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_stack":[{"ecosystem":"Red Hat:service_mesh:1.1::el8","package":"servicemesh-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.1.5-1.el8"}]}],"fixed":["0:1.1.5-1.el8"],"provider":"redhat-vex","source":"CVE-2020-15104","relation":"self"},{"ecosystem":"Red Hat:service_mesh:1.1::el8","package":"servicemesh-proxy","purl":"pkg:rpm/redhat/servicemesh-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.1.5-1.el8"}]}],"fixed":["0:1.1.5-1.el8"],"provider":"osv","source":"RHSA-2020:3090","relation":"self"}],"affected_other":[{"ecosystem":"Bitnami","package":"envoy","purl":"pkg:bitnami/envoy","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.12.6"},{"introduced":"1.13.0"},{"fixed":"1.13.4"},{"introduced":"1.14.0"},{"fixed":"1.14.4"}]}],"fixed":["1.12.6","1.13.4","1.14.4"],"provider":"osv","source":"BIT-envoy-2020-15104","relation":"self"},{"ecosystem":"CVE","package":"envoyproxy/envoy","versions":["< 1.12.6",">= 1.13.0, < 1.13.4",">= 1.14.0, < 1.14.4"],"provider":"cvelistv5","source":"CVE-2020-15104","relation":"self"},{"ecosystem":"NVD","package":"envoyproxy:envoy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.12.6"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.13.0"},{"fixed":"1.13.4"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.14.0"},{"fixed":"1.14.4"}]}],"fixed":["1.12.6","1.13.4","1.14.4"],"provider":"nvd","source":"CVE-2020-15104","relation":"self"}],"product_status":[{"vendor":"Red Hat","product":"OpenShift Service Mesh 1.1","cpe":"cpe:/a:redhat:service_mesh:1.1::el8","status":"fixed","packages":["servicemesh-proxy"],"package_count":1,"fixed":["servicemesh-proxy-1.1.5-1.el8"],"advisories":["RHSA-2020:3090"],"provider":"redhat-vex","source":"CVE-2020-15104"}],"records":[{"provider":"cvelistv5","source_id":"CVE-2020-15104","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2020-15104","license":"CC-BY-4.0","published_at":"2020-07-14T22:05:14Z","modified_at":"2024-08-04T13:08:22.235Z","summary":"TLS Validation Vulnerability in Envoy","details":"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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:N","source":"CVE-2020-15104"}],"affected":[{"ecosystem":"CVE","package":"envoyproxy/envoy","versions":["< 1.12.6",">= 1.13.0, < 1.13.4",">= 1.14.0, < 1.14.4"],"provider":"cvelistv5","source":"CVE-2020-15104","relation":"self"}],"product_status":[],"references":[{"type":"WEB","url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-w5f5-6qhq-hhrg"}]},{"provider":"nvd","source_id":"CVE-2020-15104","relation":"self","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-15104","severity":[],"affected":[{"ecosystem":"NVD","package":"envoyproxy:envoy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.12.6"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.13.0"},{"fixed":"1.13.4"}]},{"type":"ECOSYSTEM","events":[{"introduced":"1.14.0"},{"fixed":"1.14.4"}]}],"fixed":["1.12.6","1.13.4","1.14.4"],"provider":"nvd","source":"CVE-2020-15104","relation":"self"}],"product_status":[],"references":[]},{"provider":"osv","source_id":"BIT-envoy-2020-15104","relation":"self","url":"https://osv.dev/vulnerability/BIT-envoy-2020-15104","license":"Apache-2.0","published_at":"2024-03-06T11:00:31.369Z","modified_at":"2026-09-08T08:47:07.47094Z","summary":"TLS Validation Vulnerability in Envoy","details":"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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","source":"BIT-envoy-2020-15104"}],"affected":[{"ecosystem":"Bitnami","package":"envoy","purl":"pkg:bitnami/envoy","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.12.6"},{"introduced":"1.13.0"},{"fixed":"1.13.4"},{"introduced":"1.14.0"},{"fixed":"1.14.4"}]}],"fixed":["1.12.6","1.13.4","1.14.4"],"provider":"osv","source":"BIT-envoy-2020-15104","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-w5f5-6qhq-hhrg"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-15104"}]},{"provider":"osv","source_id":"RHSA-2020:3090","relation":"self","url":"https://osv.dev/vulnerability/RHSA-2020:3090","license":"CC-BY-4.0","published_at":"2024-09-16T04:36:33Z","modified_at":"2026-03-18T11:30:59.285432Z","summary":"Red Hat Security Advisory: Red Hat OpenShift Service Mesh 1.1 servicemesh-proxy security update","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N","source":"RHSA-2020:3090"}],"affected":[{"ecosystem":"Red Hat:service_mesh:1.1::el8","package":"servicemesh-proxy","purl":"pkg:rpm/redhat/servicemesh-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.1.5-1.el8"}]}],"fixed":["0:1.1.5-1.el8"],"provider":"osv","source":"RHSA-2020:3090","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://access.redhat.com/errata/RHSA-2020:3090"},{"type":"ARTICLE","url":"https://access.redhat.com/security/updates/classification/#moderate"},{"type":"REPORT","url":"https://bugzilla.redhat.com/show_bug.cgi?id=1856232"},{"type":"ADVISORY","url":"https://security.access.redhat.com/data/csaf/v2/advisories/2020/rhsa-2020_3090.json"},{"type":"REPORT","url":"https://access.redhat.com/security/cve/CVE-2020-15104"},{"type":"ADVISORY","url":"https://www.cve.org/CVERecord?id=CVE-2020-15104"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-15104"},{"type":"ARTICLE","url":"https://istio.io/latest/news/security/istio-security-2020-008/"}]},{"provider":"redhat-vex","source_id":"CVE-2020-15104","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2020-15104","license":"CC-BY-4.0","published_at":"2020-07-08T00:00:00Z","modified_at":"2021-02-16T19:41:25Z","summary":"envoyproxy/envoy: incorrectly validates TLS certificates when using wildcards for DNS SAN's","details":"An improper certificate validation vulnerability was found in envoyproxy/envoy, when externally created certificates with wildcards in the DNS Subject Alternative Name are used. This flaw allows an attacker to subvert the envoy filter or destination rules to access restricted resources. The highest threat from this vulnerability is to confidentiality.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:N","source":"CVE-2020-15104"},{"type":"Red Hat","score":"Moderate","source":"CVE-2020-15104"}],"affected":[{"ecosystem":"Red Hat:service_mesh:1.1::el8","package":"servicemesh-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0:1.1.5-1.el8"}]}],"fixed":["0:1.1.5-1.el8"],"provider":"redhat-vex","source":"CVE-2020-15104","relation":"self"}],"product_status":[{"vendor":"Red Hat","product":"OpenShift Service Mesh 1.1","cpe":"cpe:/a:redhat:service_mesh:1.1::el8","status":"fixed","packages":["servicemesh-proxy"],"package_count":1,"fixed":["servicemesh-proxy-1.1.5-1.el8"],"advisories":["RHSA-2020:3090"],"provider":"redhat-vex","source":"CVE-2020-15104"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2020/cve-2020-15104.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2020-15104"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=1856232"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2020-15104"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-15104"},{"type":"WEB","url":"https://istio.io/latest/news/security/istio-security-2020-008/"}]}],"references":[{"type":"WEB","url":"https://github.com/envoyproxy/envoy/security/advisories/GHSA-w5f5-6qhq-hhrg"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-15104"},{"type":"ADVISORY","url":"https://access.redhat.com/errata/RHSA-2020:3090"},{"type":"ARTICLE","url":"https://access.redhat.com/security/updates/classification/#moderate"},{"type":"REPORT","url":"https://bugzilla.redhat.com/show_bug.cgi?id=1856232"},{"type":"ADVISORY","url":"https://security.access.redhat.com/data/csaf/v2/advisories/2020/rhsa-2020_3090.json"},{"type":"REPORT","url":"https://access.redhat.com/security/cve/CVE-2020-15104"},{"type":"ADVISORY","url":"https://www.cve.org/CVERecord?id=CVE-2020-15104"},{"type":"ARTICLE","url":"https://istio.io/latest/news/security/istio-security-2020-008/"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2020/cve-2020-15104.json"}],"sources":[{"provider":"cvelistv5","source_id":"CVE-2020-15104","url":"https://www.cve.org/CVERecord?id=CVE-2020-15104","license":"CC-BY-4.0","modified_at":"2024-08-04T13:08:22.235Z","relation":"self"},{"provider":"nvd","source_id":"CVE-2020-15104","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-15104","relation":"self"},{"provider":"osv","source_id":"BIT-envoy-2020-15104","url":"https://osv.dev/vulnerability/BIT-envoy-2020-15104","license":"Apache-2.0","modified_at":"2026-09-08T08:47:07.47094Z","relation":"self"},{"provider":"osv","source_id":"RHSA-2020:3090","url":"https://osv.dev/vulnerability/RHSA-2020:3090","license":"CC-BY-4.0","modified_at":"2026-03-18T11:30:59.285432Z","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2020-15104","url":"https://access.redhat.com/security/cve/CVE-2020-15104","license":"CC-BY-4.0","modified_at":"2021-02-16T19:41:25Z","relation":"self"}]}
