{"id":"CVE-2020-11767","aliases":["BIT-envoy-2020-11767"],"summary":"Istio through 1.5.1 and Envoy through 1.14.1 have a data-leak issue.","published_at":"2020-04-14T00:00:00Z","modified_at":"2026-09-08T08:47:08.112856Z","products":[{"slug":"istio","name":"Istio","category":"kubernetes-container"},{"slug":"rhel","name":"Red Hat Enterprise Linux","category":"red-hat"}],"rating":{"severity":"low","score":3.1,"vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N","attack_path":"internet_unauthenticated","user_interaction":true,"malicious":false,"red_hat":"Low","vendor_ratings":[{"source":"Red Hat","rating":"Low"}]},"fix_available":false,"kev":{"listed":false,"ransomware":false},"public_exploit":false,"exploits":[],"epss":{"score":0.01817999966442585,"percentile":0.7919099926948547,"date":"2026-11-19T00:00:00Z"},"priority":4.6,"details":"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.","affected_stack":[{"ecosystem":"NVD","package":"istio:istio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.5.1"}]}],"provider":"nvd","source":"CVE-2020-11767","relation":"self"},{"ecosystem":"Red Hat:service_mesh:1","package":"servicemesh-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"provider":"redhat-vex","source":"CVE-2020-11767","relation":"self"}],"affected_other":[{"ecosystem":"Bitnami","package":"envoy","purl":"pkg:bitnami/envoy","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.14.2"}]}],"fixed":["1.14.2"],"provider":"osv","source":"BIT-envoy-2020-11767","relation":"self"},{"ecosystem":"NVD","package":"envoyproxy:envoy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.14.1"}]}],"provider":"nvd","source":"CVE-2020-11767","relation":"self"}],"product_status":[{"vendor":"Red Hat","product":"OpenShift Service Mesh 1","cpe":"cpe:/a:redhat:service_mesh:1","status":"affected","packages":["servicemesh-proxy"],"package_count":1,"fixed":[],"advisories":[],"note":"Affected","provider":"redhat-vex","source":"CVE-2020-11767"}],"records":[{"provider":"cvelistv5","source_id":"CVE-2020-11767","relation":"self","url":"https://www.cve.org/CVERecord?id=CVE-2020-11767","license":"CC-BY-4.0","published_at":"2020-04-15T01:05:38Z","modified_at":"2024-08-04T11:41:59.75Z","summary":"Istio through 1.5.1 and Envoy through 1.14.1 have a data-leak issue.","details":"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.","severity":[],"affected":[],"product_status":[],"references":[{"type":"WEB","url":"https://bugs.chromium.org/p/chromium/issues/detail?id=954160#c5"},{"type":"WEB","url":"https://github.com/envoyproxy/envoy/issues/6767"},{"type":"WEB","url":"https://github.com/istio/istio/issues/9429"},{"type":"WEB","url":"https://github.com/istio/istio/issues/13589"}]},{"provider":"nvd","source_id":"CVE-2020-11767","relation":"self","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-11767","severity":[],"affected":[{"ecosystem":"NVD","package":"envoyproxy:envoy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.14.1"}]}],"provider":"nvd","source":"CVE-2020-11767","relation":"self"},{"ecosystem":"NVD","package":"istio:istio","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"last_affected":"1.5.1"}]}],"provider":"nvd","source":"CVE-2020-11767","relation":"self"}],"product_status":[],"references":[]},{"provider":"osv","source_id":"BIT-envoy-2020-11767","relation":"self","url":"https://osv.dev/vulnerability/BIT-envoy-2020-11767","license":"Apache-2.0","published_at":"2024-03-06T11:01:15.092Z","modified_at":"2026-09-08T08:47:08.112856Z","details":"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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N","source":"BIT-envoy-2020-11767"}],"affected":[{"ecosystem":"Bitnami","package":"envoy","purl":"pkg:bitnami/envoy","ranges":[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.14.2"}]}],"fixed":["1.14.2"],"provider":"osv","source":"BIT-envoy-2020-11767","relation":"self"}],"product_status":[],"references":[{"type":"ADVISORY","url":"https://bugs.chromium.org/p/chromium/issues/detail?id=954160#c5"},{"type":"ADVISORY","url":"https://github.com/envoyproxy/envoy/issues/6767"},{"type":"ADVISORY","url":"https://github.com/istio/istio/issues/13589"},{"type":"ADVISORY","url":"https://github.com/istio/istio/issues/9429"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-11767"}]},{"provider":"redhat-vex","source_id":"CVE-2020-11767","relation":"self","url":"https://access.redhat.com/security/cve/CVE-2020-11767","license":"CC-BY-4.0","published_at":"2020-04-14T00:00:00Z","modified_at":"2024-08-02T22:00:49.261682Z","summary":"istio/envoy: forward proxy between the victim and the origin leads to information disclosure","details":"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.","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N","source":"CVE-2020-11767"},{"type":"Red Hat","score":"Low","source":"CVE-2020-11767"}],"affected":[{"ecosystem":"Red Hat:service_mesh:1","package":"servicemesh-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"}]}],"provider":"redhat-vex","source":"CVE-2020-11767","relation":"self"}],"product_status":[{"vendor":"Red Hat","product":"OpenShift Service Mesh 1","cpe":"cpe:/a:redhat:service_mesh:1","status":"affected","packages":["servicemesh-proxy"],"package_count":1,"fixed":[],"advisories":[],"note":"Affected","provider":"redhat-vex","source":"CVE-2020-11767"}],"references":[{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2020/cve-2020-11767.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2020-11767"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=1848612"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2020-11767"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-11767"},{"type":"WEB","url":"https://github.com/envoyproxy/envoy/issues/6767"}]}],"references":[{"type":"WEB","url":"https://bugs.chromium.org/p/chromium/issues/detail?id=954160#c5"},{"type":"WEB","url":"https://github.com/envoyproxy/envoy/issues/6767"},{"type":"WEB","url":"https://github.com/istio/istio/issues/9429"},{"type":"WEB","url":"https://github.com/istio/istio/issues/13589"},{"type":"WEB","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-11767"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2020/cve-2020-11767.json"},{"type":"WEB","url":"https://access.redhat.com/security/cve/CVE-2020-11767"},{"type":"WEB","url":"https://bugzilla.redhat.com/show_bug.cgi?id=1848612"},{"type":"WEB","url":"https://www.cve.org/CVERecord?id=CVE-2020-11767"}],"sources":[{"provider":"cvelistv5","source_id":"CVE-2020-11767","url":"https://www.cve.org/CVERecord?id=CVE-2020-11767","license":"CC-BY-4.0","modified_at":"2024-08-04T11:41:59.75Z","relation":"self"},{"provider":"nvd","source_id":"CVE-2020-11767","url":"https://nvd.nist.gov/vuln/detail/CVE-2020-11767","relation":"self"},{"provider":"osv","source_id":"BIT-envoy-2020-11767","url":"https://osv.dev/vulnerability/BIT-envoy-2020-11767","license":"Apache-2.0","modified_at":"2026-09-08T08:47:08.112856Z","relation":"self"},{"provider":"redhat-vex","source_id":"CVE-2020-11767","url":"https://access.redhat.com/security/cve/CVE-2020-11767","license":"CC-BY-4.0","modified_at":"2024-08-02T22:00:49.261682Z","relation":"self"}]}
