Information disclosure via unencrypted pod responses
Published Feb 20, 2024 · Updated Aug 1, 2024
Missing encryption in Cilium 1.14.0 through 1.14.6 allows adjacent attackers to read pod responses to Ingress and health endpoints. The eBPF dataplane leaves the pod-to-endpoint response path outside WireGuard encryption; published material does not identify the responsible function. The issue requires CRD-backed state and WireGuard transparent encryption; the opposite traffic direction is unaffected, and health traffic is internal.
Summary
What happened
Missing encryption in Cilium 1.14.0 through 1.14.6 allows adjacent attackers to read pod responses to Ingress and health endpoints. The eBPF dataplane leaves the pod-to-endpoint response path outside WireGuard encryption; published material does not identify the responsible function. The issue requires CRD-backed state and WireGuard transparent encryption; the opposite traffic direction is unaffected, and health traffic is internal.
The record
- CVE
- CVE-2024-25630
- Published
- Feb 20, 2024
- Updated
- Aug 1, 2024
- Vendor
- Cilium
- Product
- Cilium
- Classifications
- CWE-311, CWE-319, T1040
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 20, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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.0, < 1.14.7
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