An issue was discovered in Envoy 1.12.0. An untrusted remote client may send an HTTP header (such as Host) with whitespace after the header content. Envoy will treat "header-value " as a different string from "header-value" so for example with the Host header "example.com " one could bypass "example.com" matchers.
https://groups.google.com/forum/#%21forum/envoy-users
https://github.com/envoyproxy/envoy/security/advisories/GHSA-356m-vhw2-wcm4
https://github.com/envoyproxy/envoy/commits/master
http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00034.html