Red Hat Security Advisory: Red Hat OpenShift Service Mesh 1.0.7 servicemesh-proxy security update
🔗 CVE IDs covered (1)
📋 Description
CVE-2020-8595 — istio: unauthorised access to JWT protected HTTP path
🎯 Affected products3
- OpenShift Service Mesh 1.0
- servicemesh-proxy-0:1.0.7-1.el8.src as a component of OpenShift Service Mesh 1.0
- servicemesh-proxy-0:1.0.7-1.el8.x86_64 as a component of OpenShift Service Mesh 1.0
✅ Remediation
The OpenShift Service Mesh release notes provide information on the features and known issues: https://docs.openshift.com/container-platform/4.3/service_mesh/servicemesh-release-notes.html Workaround: Depending on the paths used in the exact match clause, it is possible to update the path to a regex. As provided by the Istio Product Committee, the following mitigation can be employed. The original policy specifying a JWT protected path is as follows: --- apiVersion: "authentication.istio.io/v1alpha1" kind: "Policy" metadata: name: "jwt-example" namespace: istio-system spec: targets: - name: istio-ingressgateway origins: - jwt: issuer: "[email protected]" jwksUri: "https://raw.githubusercontent.com/istio/istio/release-1.4/security/tools/jwt/samples/jwks.json" trigger_rules: - included_paths: - exact: /productpage The exact path definition can then be updated to a regular expression: --- - jwt: issuer: "[email protected]" jwksUri: "https://raw.githubusercontent.com/istio/istio/release-1.4/security/tools/jwt/samples/jwks.json" trigger_rules: - included_paths: - regex: '/productpage(\?.*)?' - regex: '/productpage(#.*)?'