KubeEdge: Command Injection in NodeUpgradeJob - RCE on edge nodes via v1alpha2 API
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.21.2, 1.22.2, 1.23.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
KubeEdge is an open source system for extending native containerized application orchestration capabilities to hosts at Edge. From 1.12.0 until 1.21.2, 1.22.2, and 1.23.1, the v1alpha2 NodeUpgradeJob handler in edge/pkg/taskmanager/actions/nodeupgradejob.go concatenates authenticated user-controlled spec.version and spec.image values into the keadm upgrade edge shell command. A user with permission to create or update NodeUpgradeJob resources can supply shell metacharacters in either field, causing arbitrary commands to execute on targeted edge nodes with the privileges of the upgrade process and compromising node confidentiality, integrity, and availability. This issue is fixed in versions 1.21.2, 1.22.2, and 1.23.1.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- kubeedge kubeedge
From 1.12.0 · fixed in 1.21.2; From 1.22.0 · fixed in 1.22.2; From 1.23.0 · fixed in 1.23.1
- github.com/kubeedge/kubeedgeGo
From 1.12.0 · fixed in 1.21.2; From 1.22.0 · fixed in 1.22.2; From 1.23.0 · fixed in 1.23.1
- github.com/kubeedge/kubeedgeGo
From 1.12.0 · fixed in 1.21.2
- github.com/kubeedge/kubeedgeGo
From 1.22.0 · fixed in 1.22.2
- github.com/kubeedge/kubeedgeGo
From 1.23.0 · fixed in 1.23.1