QID 355316

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. (
( CVE-2023-27487) 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, escalation of privileges is possible when `failure_mode_allow: true` is configured for `ext_authz` filter.
For affected components that are used for logging and/or visibility, requests may not be logged by the receiving service.
When envoy was configured to use ext_authz, ext_proc, tap, ratelimit filters, and grpc access log service and an http header with non-utf-8 data was received, envoy would generate an invalid protobuf message and send it to the configured service.
The receiving service would typically generate an error when decoding the protobuf message.
For ext_authz that was configured with ``failure_mode_allow: true``, the request would have been allowed in this case.
` character.
( CVE-2023-27496)

Successful exploitation of this vulnerability could lead to a securitybreach or could affect integrity, availability, and confidentiality.