Workaround for potential to manipulate `x-envoy` headers from external sources

Solution Verified - Updated -

Issue

  • When an OpenShift Cluster is installed and the Service and Cluster network CIDR range falls within the RFC1918 address range, then an external client or browser can set envoy headers and manipulate the integrity of the envoy logs in the ingress gateway and the sidecar of the target service being called.

  • This does not happen when the OpenShift Cluster is not installed within the RFC 1918 ranges (10/8 prefix, 172.16/12 prefix, 192.168/16 prefix).

Environment

  • Red Hat OpenShift Service Mesh
    • 2.4

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content