CVE-2024-42487 json
Cilium's Gateway API route matching order contradicts specification
published 2024-08-15 2 y ago modified 2026-09-10 1 mo ago also BIT-cilium-2024-42487 , BIT-cilium-operator-2024-42487 , BIT-hubble-relay-2024-42487 , EUVD-2024-2632 , GHSA-qcm3-7879-xcww , GO-2024-3071
- cvss
- 4.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 45%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/cilium/cilium 1.15.8, 1.16.1
- bitnami cilium 1.16.1
- bitnami cilium-operator 1.16.1
- bitnami hubble-relay 1.16.1
- cilium cilium 1.15.8, 1.16.1
- github.com/cilium/cilium@a3510fe commit
- github.com/cilium/cilium@d88772b commit
- github.com/cilium/cilium@fe42273 commit
- github.com/cilium/cilium#34109 pull request
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
0.53% chance of exploitation in the next 30 days, higher than 45% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N |
| GitHub | 3.1 | 4.0 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:N |
| NVD | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
| OSV | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/cilium/cilium | >=1.16.0, <1.16.1 >=1.15.0, <1.15.8 |
1.16.1 1.15.8 |
| bitnami | cilium | >=1.15.0, <1.16.1 |
1.16.1 |
| bitnami | cilium-operator | >=1.15.4, <1.16.1 |
1.16.1 |
| bitnami | hubble-relay | >=1.15.0, <1.16.1 |
1.16.1 |
Affected products
- cilium cilium
Classification
References
-
github.com
/cilium/cilium/pull/34109
web, patch, third-party-advisory, advisory
-
github.com
/cilium/cilium/commit/a3510fe4a92305822aa1a5e08cb6d6c873c8699a
web, patch, third-party-advisory, advisory
-
github.com
/cilium/cilium/commit/d88772b9c29e370becbc4547cada6711d51edcde
web, patch
-
github.com
/cilium/cilium/commit/fe42273566a943a0f3174c87b23a195c856b51d6
web, patch
-
github.com
/cilium/cilium/security/advisories/GHSA-qcm3-7879-xcww
web, vendor-advisory, advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-42487
advisory, web
-
github.com
/cilium/cilium
package
Sources
- CVE List CVE-2024-42487
- GitHub Advisory GHSA-qcm3-7879-xcww
- NVD CVE-2024-42487
- OSV BIT-cilium-2024-42487
- OSV BIT-cilium-operator-2024-42487
- OSV BIT-hubble-relay-2024-42487
- OSV GO-2024-3071
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.