CVE-2024-42486

Cilium vulnerable to information leakage via incorrect ReferenceGrant update logic in Gateway API

CVSS 3.1 5.4 MEDIUMEUVD CVSS 3.1 5.4 CVSS 3.1 · [email protected] · Secondary 5.4 MEDIUMCVSS 3.1 · [email protected] · Primary 7.2 HIGHCVSS_V3 Publisher rating MODERATEFixed by github.com/cilium/cilium 1.16.1 Fixed by github.com/cilium/cilium 1.15.8osv · severity unknownFixed by github.com/cilium/cilium 1.15.8 Fixed by github.com/cilium/cilium 1.16.1KEV status unknown

Original advisory

cve-program · CVE-2024-42486

Published

Cilium is a networking, observability, and security solution with an eBPF-based dataplane. In versions on the 1.15.x branch prior to 1.15.8 and the 1.16.x branch prior to 1.16.1, ReferenceGrant changes are not correctly propagated in Cilium's GatewayAPI controller, which could lead to Gateway resources being able to access secrets for longer than intended, or to Routes having the ability to forward traffic to backends in other namespaces for longer than intended. This issue has been patched in Cilium v1.15.8 and v1.16.1. As a workaround, any modification of a related Gateway/HTTPRoute/GRPCRoute/TCPRoute CRD (for example, adding any label to any of these resources) will trigger a reconciliation of ReferenceGrants on an affected cluster.

Read the publisher's advisory

euvd · EUVD-2024-2669

Published

Read the publisher's advisory

nvd · CVE-2024-42486

Published

Read the publisher's advisory

osv · GHSA-vwf8-q6fw-4wcm

Published

### Impact Due to ReferenceGrant changes not being immediately propagated in Cilium's GatewayAPI controller, Gateway resources are able to access secrets in other namespaces after the associated ReferenceGrant has been revoked. This can lead to Gateways continuing to establish sessions using secrets that they should no longer have access to. ### Patches This issue was resolved in https://github.com/cilium/cilium/pull/34032. This issue affects: - Cilium v1.15 between v1.15.0 and v1.15.7 inclusive - Cilium v1.16.0 This issue has been patched in: - Cilium v1.15.8 - Cilium v1.16.1 ### Workarounds Any modification of a related Gateway/HTTPRoute/GRPCRoute/TCPRoute CRD (for example, adding any label to any of these resources) will trigger a reconciliation of ReferenceGrants on an affected cluster. ### Acknowledgements The Cilium community has worked together with members of Cure53 and Isovalent to prepare these mitigations. Special thanks to @sayboras for resolving this issue. ### For more information If you have any questions or comments about this advisory, please reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack). If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [[email protected]](mailto:[email protected]). This is a private mailing list for the Cilium security team, and your report will be treated as top priority.

Read the publisher's advisory

osv · GO-2024-3074

Published

Cilium leaks information via incorrect ReferenceGrant update logic in Gateway API in github.com/cilium/cilium

Read the publisher's advisory

Affected versions, risk and source history

cve-program · CVE-2024-42486

Published

cilium

Vendor product

Publisher's version information

Shown as published. These rules are not interpreted as NuGet package version ranges.

{
                    "vendor": "cilium",
                    "product": "cilium",
                    "versions": [
                        {
                            "version": "= 1.16.0",
                            "status": "affected"
                        },
                        {
                            "version": ">= 1.15.0, < 1.15.8",
                            "status": "affected"
                        }
                    ]
                }

Original source record · Cite this exact observation · Complete original publisher JSON

euvd · EUVD-2024-2669

Published

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Aug 16, 2024, 2:34:41 PM

dateUpdated: Aug 16, 2024, 2:54:16 PM

No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.

Original source record · Cite this exact observation · Complete original publisher JSON

nvd · CVE-2024-42486

Published

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Analyzed

Weakness classifications: CWE-200

Original publisher date fields

published: 2024-08-16T15:15:28.777

lastModified: 2026-06-17T07:49:32.653

2 source CPE criteria · context only

cpe:2.3:a:cilium:cilium:*:*:*:*:*:*:*:*
cpe:2.3:a:cilium:cilium:1.16.0:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GHSA-vwf8-q6fw-4wcm

Published

github.com/cilium/cilium

SEMVER · introduced 1.16.0 → fixed 1.16.1

1 versions listed as affected

1.16.0

github.com/cilium/cilium

SEMVER · introduced 1.15.0 → fixed 1.15.8

Original source record · Cite this exact observation · Complete original publisher JSON

osv · GO-2024-3074

Published

github.com/cilium/cilium

SEMVER · introduced 1.15.0 → fixed 1.15.8 → introduced 1.16.0 → fixed 1.16.1

Original source record · Cite this exact observation · Complete original publisher JSON