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.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Envoy | Envoyproxy | * | 1.12.1 (including) |
| Openshift Service Mesh 1.0 | RedHat | kiali-0:v1.0.8.redhat1-1.el7 | * |
| OpenShift Service Mesh 1.0 | RedHat | servicemesh-0:1.0.3-1.el8 | * |
| OpenShift Service Mesh 1.0 | RedHat | servicemesh-cni-0:1.0.3-1.el8 | * |
| OpenShift Service Mesh 1.0 | RedHat | servicemesh-grafana-0:6.2.2-25.el8 | * |
| OpenShift Service Mesh 1.0 | RedHat | servicemesh-operator-0:1.0.3-1.el8 | * |
| OpenShift Service Mesh 1.0 | RedHat | servicemesh-prometheus-0:2.7.2-26.el8 | * |
| OpenShift Service Mesh 1.0 | RedHat | servicemesh-proxy-0:1.0.3-1.el8 | * |
References
- http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00034.html
- https://blog.envoyproxy.io
- https://github.com/envoyproxy/envoy/commits/master
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-356m-vhw2-wcm4
- https://groups.google.com/forum/#%21forum/envoy-users
- http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00034.html
- https://blog.envoyproxy.io
- https://github.com/envoyproxy/envoy/commits/master
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-356m-vhw2-wcm4
- https://groups.google.com/forum/#%21forum/envoy-users