Cilium up to 1.15.7/1.16.0 HTTPRoutes/GRPCRoutes response splitting

Summaryinfo

A vulnerability marked as problematic has been reported in Cilium up to 1.15.7/1.16.0. This issue affects some unknown processing of the component HTTPRoutes/GRPCRoutes. The manipulation leads to response splitting. This vulnerability is uniquely identified as CVE-2024-42487. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Cilium up to 1.15.7/1.16.0. This issue affects an unknown code of the component HTTPRoutes/GRPCRoutes. The manipulation with an unknown input leads to a response splitting vulnerability. Using CWE to declare the problem leads to CWE-113. The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers. Impacted is confidentiality. The summary by CVE is:

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In the 1.15 branch prior to 1.15.8 and the 1.16 branch prior to 1.16.1, Gateway API HTTPRoutes and GRPCRoutes do not follow the match precedence specified in the Gateway API specification. In particular, request headers are matched before request methods, when the specification describes that the request methods must be respected before headers are matched. This could result in unexpected behaviour with security This issue is fixed in Cilium v1.15.8 and v1.16.1. There is no workaround for this issue.

The advisory is shared at github.com. The identification of this vulnerability is CVE-2024-42487 since 08/02/2024. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 1.15.8 or 1.16.1 eliminates this vulnerability. Applying the patch a3510fe4a92305822aa1a5e08cb6d6c873c8699a is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

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

Productinfo

Name

• Cilium

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.15.0
• 1.15.1
• 1.15.2
• 1.15.3
• 1.15.4
• 1.15.5
• 1.15.6
• 1.15.7
• 1.16.0

License

• open-source

Website

• Product: https://github.com/cilium/cilium/

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