An authenticated OS command injection vulnerability in KubeEdge allows attackers to gain full control over edge nodes, posing a severe risk to cluster integrity and confidentiality.

The v1alpha2 NodeUpgradeJob handler fails to properly sanitize user-controlled spec.version and spec.image fields before concatenating them into a shell command. An attacker with privileges to create or update NodeUpgradeJob resources can inject shell metacharacters to execute arbitrary code on targeted edge nodes.

The ability to execute arbitrary commands on edge nodes allows an attacker to compromise node confidentiality, integrity, and availability. Given the CVSS score of 8.8, this high-severity vulnerability could lead to lateral movement within the infrastructure, data exfiltration, or the total disruption of edge-based containerized workloads.

Immediate Action: Upgrade KubeEdge to versions 1.21.2, 1.22.2, or 1.23.1 as specified in the official vendor security advisory.

Proactive Monitoring: Review audit logs for unauthorized or suspicious NodeUpgradeJob resource creation and monitor edge node process execution for unexpected shell activity.

Compensating Controls: Implement strict Kubernetes RBAC policies to restrict which users have the authority to create or update NodeUpgradeJob resources, effectively reducing the attack surface.

Public Exploit Available: No (exploit_available: false)

This vulnerability represents a critical security gap for KubeEdge deployments. Administrators must prioritize patching the affected software to the stated fixed versions immediately to prevent potential command injection attacks. Restricting access to NodeUpgradeJob resource management is a necessary secondary control to limit the impact of compromised or malicious internal accounts.