Host takeover via shared PID namespace
Published Jan 20, 2021 · Updated Aug 4, 2024
Improper privilege management in Weave Net before 2.8.0 allows attackers with pod code execution to take over Kubernetes hosts. The supplied DaemonSet unnecessarily places privileged networking pods in the host PID namespace and mounts host paths, exposing host processes and writable root-filesystem locations. Exploitation requires a separate flaw or misconfiguration that grants code execution inside a Weave Net pod; the resulting access permits control of any cluster host.
Summary
What happened
Improper privilege management in Weave Net before 2.8.0 allows attackers with pod code execution to take over Kubernetes hosts. The supplied DaemonSet unnecessarily places privileged networking pods in the host PID namespace and mounts host paths, exposing host processes and writable root-filesystem locations. Exploitation requires a separate flaw or misconfiguration that grants code execution inside a Weave Net pod; the resulting access permits control of any cluster host.
The record
- CVE
- CVE-2020-26278
- Published
- Jan 20, 2021
- Updated
- Aug 4, 2024
- Vendor
- Weaveworks
- Product
- Weave Net
- Classifications
- CWE-250, T1611
- Attack vector
- adjacent
- Privileges
- Unavailable
Timeline
How it unfolded
- Jan 20, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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=< 2.8.0
What conditions does exploitation require?
What is affected?
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.
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