cve.bz

CVE-2024-42487 cilium cilium: Interpretation Conflict

4.3 mediumEPSS 0.5%Fix available

Medium (4.3) in cilium cilium. EPSS 0.5% estimated probability of exploitation activity in the next 30 days. Fixed in github.com/cilium/cilium 1.15.8, 1.16.1.

On this page
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.

Severity

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 46th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2024-08-15. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-436 Interpretation Conflict
CWE-113 Improper Neutralization of CRLF Sequences in HTTP Headers (HTTP Request Splitting)
OWASP Top 10
A05:2025 Injection, A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2024-42487 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-42487?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-42487?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2024-42487 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
cilium:ciliumfrom 1.15.0 before 1.15.8
cilium:cilium1.16.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-qcm3-7879-xcwwGogithub.com/cilium/cilium>=1.16.0 <1.16.11.16.1
GHSA-qcm3-7879-xcwwGogithub.com/cilium/cilium>=1.15.0 <1.15.81.15.8
GO-2024-3071Gogithub.com/cilium/cilium>=1.15.0 <1.15.8
>=1.16.0 <1.16.1
1.15.8, 1.16.1

Attack patterns (CAPEC)

  • CAPEC-34 HTTP Response Splitting Likelihood: Medium · Severity: High
  • CAPEC-105 HTTP Request Splitting Likelihood: Medium · Severity: High
  • CAPEC-273 HTTP Response Smuggling Likelihood: Medium · Severity: High
  • CAPEC-31 Accessing/Intercepting/Modifying HTTP Cookies Likelihood: High · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON