Envoy up to 1.25.x JSON Web Token input validation

Summaryinfo

A vulnerability classified as problematic has been found in Envoy up to 1.22.8/1.23.5/1.24.3/1.25.2/1.25.x. This impacts an unknown function of the component JSON Web Token Handler. Performing a manipulation results in input validation. This vulnerability is reported as CVE-2023-27487. The attack is possible to be carried out remotely. No exploit exists. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability classified as problematic has been found in Envoy up to 1.22.8/1.23.5/1.24.3/1.25.2/1.25.x. This affects some unknown processing of the component JSON Web Token Handler. The manipulation with an unknown input leads to a input validation vulnerability. CWE is classifying the issue as CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was disclosed 04/04/2023 as GHSA-5375-pq35-hf2g. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-27487 since 03/01/2023. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.22.9, 1.23.6, 1.24.4, 1.25.3 or 1.26.0 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

• Envoy

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5
• 1.6
• 1.7
• 1.8
• 1.9
• 1.10
• 1.11
• 1.12
• 1.13
• 1.14
• 1.15
• 1.16
• 1.17
• 1.18
• 1.19
• 1.20
• 1.21
• 1.22
• 1.22.0
• 1.22.1
• 1.22.2
• 1.22.3
• 1.22.4
• 1.22.5
• 1.22.6
• 1.22.7
• 1.22.8
• 1.23
• 1.23.0
• 1.23.1
• 1.23.2
• 1.23.3
• 1.23.4
• 1.23.5
• 1.24
• 1.24.0
• 1.24.1
• 1.24.2
• 1.24.3
• 1.25
• 1.25.0
• 1.25.1
• 1.25.2

License

• free

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion