First published: Thu Mar 16 2023(Updated: )
Envoy is an open source edge and service proxy designed for cloud-native applications. Prior to versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9, the client may bypass JSON Web Token (JWT) checks and forge fake original paths. The header `x-envoy-original-path` should be an internal header, but Envoy does not remove this header from the request at the beginning of request processing when it is sent from an untrusted client. The faked header would then be used for trace logs and grpc logs, as well as used in the URL used for `jwt_authn` checks if the `jwt_authn` filter is used, and any other upstream use of the x-envoy-original-path header. Attackers may forge a trusted `x-envoy-original-path` header. Versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, and 1.22.9 have patches for this issue.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Envoyproxy Envoy | <1.22.9 | |
Envoyproxy Envoy | >=1.23.0<1.23.6 | |
Envoyproxy Envoy | >=1.24.0<1.24.4 | |
Envoyproxy Envoy | >=1.25.0<1.25.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2023-27487 is a vulnerability in Envoy that allows the client to bypass JSON Web Token (JWT) checks and forge fake original paths.
CVE-2023-27487 has a severity rating of 9.1 (Critical).
Versions 1.22.9, 1.23.0 to 1.23.6, 1.24.0 to 1.24.4, and 1.25.0 to 1.25.3 of Envoy are affected by CVE-2023-27487.
The client can bypass JWT checks in CVE-2023-27487 by using the header 'x-envoy-original-path' to forge fake original paths.
Yes, upgrading to versions 1.26.0, 1.25.3, 1.24.4, 1.23.6, or 1.22.9 of Envoy fixes the vulnerability CVE-2023-27487.