Host Firewall bypass via stale node labels
Published Aug 15, 2024 · Updated Aug 19, 2024
A race condition in Cilium before 1.14.14 and 1.15.0 through 1.15.7 allows remote attackers to bypass Host Firewall policy. During agent startup, the node-label observer advances its old-label state after a host-endpoint update fails, causing every later update to fail its precondition. The race requires the Kubernetes node watcher to initialize before the host endpoint; stale labels then prevent label-selected clusterwide policies from applying.
Summary
What happened
A race condition in Cilium before 1.14.14 and 1.15.0 through 1.15.7 allows remote attackers to bypass Host Firewall policy. During agent startup, the node-label observer advances its old-label state after a host-endpoint update fails, causing every later update to fail its precondition. The race requires the Kubernetes node watcher to initialize before the host endpoint; stale labels then prevent label-selected clusterwide policies from applying.
The record
- CVE
- CVE-2024-42488
- Published
- Aug 15, 2024
- Updated
- Aug 19, 2024
- Vendor
- Cilium
- Product
- Cilium
- Classifications
- CWE-362, T1562.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 15, 2024CVE publishedPublication date reported by the CVE source.
- Aug 19, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 1.14.14
- Affected versionversion=>= 1.15.0, < 1.15.8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo