{"api_version":"1","generated_at":"2026-04-22T21:37:53+00:00","cve":"CVE-2020-11767","urls":{"html":"https://cve.report/CVE-2020-11767","api":"https://cve.report/api/cve/CVE-2020-11767.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2020-11767","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2020-11767"},"summary":{"title":"CVE-2020-11767","description":"Istio through 1.5.1 and Envoy through 1.14.1 have a data-leak issue. If there is a TCP connection (negotiated with SNI over HTTPS) to *.example.com, a request for a domain concurrently configured explicitly (e.g., abc.example.com) is sent to the server(s) listening behind *.example.com. The outcome should instead be 421 Misdirected Request. Imagine a shared caching forward proxy re-using an HTTP/2 connection for a large subnet with many users. If a victim is interacting with abc.example.com, and a server (for abc.example.com) recycles the TCP connection to the forward proxy, the victim's browser may suddenly start sending sensitive data to a *.example.com server. This occurs because the forward proxy between the victim and the origin server reuses connections (which obeys the specification), but neither Istio nor Envoy corrects this by sending a 421 error. Similarly, this behavior voids the security model browsers have put in place between domains.","state":"PUBLIC","assigner":"cve@mitre.org","published_at":"2020-04-15 02:15:00","updated_at":"2021-07-21 11:39:00"},"problem_types":["NVD-CWE-noinfo"],"metrics":[],"references":[{"url":"https://github.com/istio/istio/issues/13589","name":"https://github.com/istio/istio/issues/13589","refsource":"MISC","tags":["Exploit","Third Party Advisory"],"title":"Istio does not adhere to HTTP/2 RFC 7540 · Issue #13589 · istio/istio · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://bugs.chromium.org/p/chromium/issues/detail?id=954160#c5","name":"https://bugs.chromium.org/p/chromium/issues/detail?id=954160#c5","refsource":"MISC","tags":["Issue Tracking","Third Party Advisory"],"title":"954160 - \n \n \n chromium -\n \n \n An open-source project to help move the web forward. - \n \n Monorail","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/envoyproxy/envoy/issues/6767","name":"https://github.com/envoyproxy/envoy/issues/6767","refsource":"MISC","tags":["Third Party Advisory"],"title":"Envoy does not adhere to HTTP/2 RFC 7540 · Issue #6767 · envoyproxy/envoy · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://github.com/istio/istio/issues/9429","name":"https://github.com/istio/istio/issues/9429","refsource":"MISC","tags":["Third Party Advisory"],"title":"404 NR when using browser on multiple ingress gateways · Issue #9429 · istio/istio · GitHub","mime":"text/html","httpstatus":"200","archivestatus":"200"},{"url":"https://www.cve.org/CVERecord?id=CVE-2020-11767","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2020-11767","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[{"cve_year":"2020","cve_id":"11767","vulnerable":"1","versionEndIncluding":"1.14.1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"envoyproxy","cpe5":"envoy","cpe6":"*","cpe7":"*","cpe8":"*","cpe9":"*","cpe10":"*","cpe11":"*","cpe12":"*","cpe13":"*"},{"cve_year":"2020","cve_id":"11767","vulnerable":"1","versionEndIncluding":"1.5.1","cpe1":"cpe","cpe2":"2.3","cpe3":"a","cpe4":"istio","cpe5":"istio","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":"cve@mitre.org","ID":"CVE-2020-11767","STATE":"PUBLIC"},"affects":{"vendor":{"vendor_data":[{"product":{"product_data":[{"product_name":"n/a","version":{"version_data":[{"version_value":"n/a"}]}}]},"vendor_name":"n/a"}]}},"data_format":"MITRE","data_type":"CVE","data_version":"4.0","description":{"description_data":[{"lang":"eng","value":"Istio through 1.5.1 and Envoy through 1.14.1 have a data-leak issue. If there is a TCP connection (negotiated with SNI over HTTPS) to *.example.com, a request for a domain concurrently configured explicitly (e.g., abc.example.com) is sent to the server(s) listening behind *.example.com. The outcome should instead be 421 Misdirected Request. Imagine a shared caching forward proxy re-using an HTTP/2 connection for a large subnet with many users. If a victim is interacting with abc.example.com, and a server (for abc.example.com) recycles the TCP connection to the forward proxy, the victim's browser may suddenly start sending sensitive data to a *.example.com server. This occurs because the forward proxy between the victim and the origin server reuses connections (which obeys the specification), but neither Istio nor Envoy corrects this by sending a 421 error. Similarly, this behavior voids the security model browsers have put in place between domains."}]},"problemtype":{"problemtype_data":[{"description":[{"lang":"eng","value":"n/a"}]}]},"references":{"reference_data":[{"url":"https://bugs.chromium.org/p/chromium/issues/detail?id=954160#c5","refsource":"MISC","name":"https://bugs.chromium.org/p/chromium/issues/detail?id=954160#c5"},{"url":"https://github.com/envoyproxy/envoy/issues/6767","refsource":"MISC","name":"https://github.com/envoyproxy/envoy/issues/6767"},{"url":"https://github.com/istio/istio/issues/9429","refsource":"MISC","name":"https://github.com/istio/istio/issues/9429"},{"url":"https://github.com/istio/istio/issues/13589","refsource":"MISC","name":"https://github.com/istio/istio/issues/13589"}]}},"nvd":{"publishedDate":"2020-04-15 02:15:00","lastModifiedDate":"2021-07-21 11:39:00","problem_types":["NVD-CWE-noinfo"],"metrics":{"baseMetricV3":{"cvssV3":{"version":"3.1","vectorString":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N","attackVector":"NETWORK","attackComplexity":"HIGH","privilegesRequired":"NONE","userInteraction":"REQUIRED","scope":"UNCHANGED","confidentialityImpact":"LOW","integrityImpact":"NONE","availabilityImpact":"NONE","baseScore":3.1,"baseSeverity":"LOW"},"exploitabilityScore":1.6,"impactScore":1.4},"baseMetricV2":{"cvssV2":{"version":"2.0","vectorString":"AV:N/AC:H/Au:N/C:P/I:N/A:N","accessVector":"NETWORK","accessComplexity":"HIGH","authentication":"NONE","confidentialityImpact":"PARTIAL","integrityImpact":"NONE","availabilityImpact":"NONE","baseScore":2.6},"severity":"LOW","exploitabilityScore":4.9,"impactScore":2.9,"acInsufInfo":false,"obtainAllPrivilege":false,"obtainUserPrivilege":false,"obtainOtherPrivilege":false,"userInteractionRequired":true}},"configurations":{"CVE_data_version":"4.0","nodes":[{"operator":"OR","children":[],"cpe_match":[{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:istio:istio:*:*:*:*:*:*:*:*","versionEndIncluding":"1.5.1","cpe_name":[]},{"vulnerable":true,"cpe23Uri":"cpe:2.3:a:envoyproxy:envoy:*:*:*:*:*:*:*:*","versionEndIncluding":"1.14.1","cpe_name":[]}]}]}},"legacy_mitre":{"record":{"CveYear":"2020","CveId":"11767","Ordinal":"172461","Title":"CVE-2020-11767","CVE":"CVE-2020-11767","Year":"2020"},"notes":[{"CveYear":"2020","CveId":"11767","Ordinal":"1","NoteData":"Istio through 1.5.1 and Envoy through 1.14.1 have a data-leak issue. If there is a TCP connection (negotiated with SNI over HTTPS) to *.example.com, a request for a domain concurrently configured explicitly (e.g., abc.example.com) is sent to the server(s) listening behind *.example.com. The outcome should instead be 421 Misdirected Request. Imagine a shared caching forward proxy re-using an HTTP/2 connection for a large subnet with many users. If a victim is interacting with abc.example.com, and a server (for abc.example.com) recycles the TCP connection to the forward proxy, the victim's browser may suddenly start sending sensitive data to a *.example.com server. This occurs because the forward proxy between the victim and the origin server reuses connections (which obeys the specification), but neither Istio nor Envoy corrects this by sending a 421 error. Similarly, this behavior voids the security model browsers have put in place between domains.","Type":"Description","Title":null},{"CveYear":"2020","CveId":"11767","Ordinal":"2","NoteData":"2020-04-14","Type":"Other","Title":"Published"},{"CveYear":"2020","CveId":"11767","Ordinal":"3","NoteData":"2020-04-14","Type":"Other","Title":"Modified"}]}}}