In Envoy 1.17.1, when a JSON Web Token (JWT) authentication filter is specified with `allow_missing`, a request with a JWT token with an incorrect issuer can bypass the filter. Upstream issue: https://github.com/istio/envoy/pull/303
Acknowledgments: Name: Istio Product Security Working Group
OpenShift ServiceMesh is not affected by this as it uses Istio v1.16.x. Comparing the code: https://github.com/maistra/envoy/blob/7f7ca9dc6df537d19e6b62eff379c0829ead9c90/source/extensions/filters/http/jwt_authn/verifier.cc#L305 It looks like the upstream fix for this CVE is pretty much restoring the original behaviour.
External References: https://github.com/envoyproxy/envoy/security/advisories/GHSA-4996-m8hf-hj27 https://istio.io/latest/news/security/istio-security-2021-001/
Upstream fix: https://github.com/envoyproxy/envoy/pull/15194
And upstream commit: https://github.com/envoyproxy/envoy/pull/15194/commits/fc1644ee11a53a60da349cacede8d6cb1d619eee
Statement: Only version 1.9.0 of upstream Istio is affected by the vulnerability. Therefore, even if the OpenShift ServiceMesh (OSSM) does package Istio, it is only v1.6.14 and is not affected.