GHSA-m3c6-2p7h-cfr3: OS Command Injection
Description
KubeEdge ConfigUpdateJob processing was vulnerable to command injection on edge nodes.
The updateFields values from a ConfigUpdateJob were concatenated into a command string and executed through a system shell. An authenticated user with sufficient permissions to create or update ConfigUpdateJob resources could include shell metacharacters in the supplied configuration fields and cause unintended commands to be executed on targeted edge nodes.
Impact
Successful exploitation could allow an authenticated attacker to execute arbitrary commands on affected edge nodes with the privileges of the KubeEdge process handling the ConfigUpdateJob.
The attacker must already have permission to create or modify ConfigUpdateJob resources and target an enrolled edge node.
Patches
The fix removes shell-based command construction and invokes keadm config-update using structured command arguments.
The complete --set value is passed as a single literal argument, preventing shell metacharacters from being interpreted as commands.
Fixes are planned for the following maintained releases:
v1.23.1 v1.22.2 v1.21.2
Workarounds
Until a patched release is available:
restrict RBAC permissions for creating or modifying ConfigUpdateJob resources; allow only trusted administrators to submit configuration update jobs; avoid using ConfigUpdateJob in environments where its input cannot be fully trusted; monitor ConfigUpdateJob resources and edge-node process activity for unexpected commands or changes.
Credits
KubeEdge thanks Sang-Hoon Choi (KoreaSecurity, Sejong University) for responsibly reporting this issue and for coordinating with the KubeEdge maintainers through the security disclosure process.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
go/github.com/kubeedge/kubeedgeto a version that resolves this vulnerability.Fixed in 1.23.1 - Upgrade
Upgrade
go/github.com/kubeedge/kubeedgeto a version that resolves this vulnerability.Fixed in 1.22.2 - Upgrade
Upgrade
go/github.com/kubeedge/kubeedgeto a version that resolves this vulnerability.Fixed in 1.21.2 - Upgrade
Upgrade
KubeEdgeto a version that resolves this vulnerability.Fixed in v1.21.2 - Upgrade
Upgrade
KubeEdgeto a version that resolves this vulnerability.Fixed in v1.22.2 - Upgrade
Upgrade
KubeEdgeto a version that resolves this vulnerability.Fixed in v1.23.1 - Compensating control
Allow only trusted administrators to submit ConfigUpdateJob resources.
- Compensating control
Avoid using ConfigUpdateJob in environments where its input cannot be fully trusted.
- Compensating control
Restrict RBAC permissions for creating or modifying ConfigUpdateJob resources.
- Compensating control
Monitor ConfigUpdateJob resources and edge-node process activity for unexpected commands or changes.
Event History
Frequently Asked Questions
Which systems are exposed to command execution?
Exposure is limited to enrolled edge nodes that can be targeted by ConfigUpdateJob resources. Commands execute with the privileges of the KubeEdge process that handles the job on the edge node.
What access must an attacker have?
The attacker must be authenticated and have sufficient permission to create or modify ConfigUpdateJob resources. They must also be able to target an enrolled edge node.
Which releases include the planned fix?
Fixes are planned for maintained releases v1.23.1, v1.22.2, and v1.21.2. The fix passes the complete --set value as one structured literal argument rather than constructing a shell command.