Attack Chain

1. An attacker, with permissions to create or modify NuclioFunctions in the Kubernetes cluster, crafts a malicious NuclioFunction definition.
2. The attacker includes a cron trigger with a specially crafted event.headers key (e.g., X-Inject"; ARBITRARY_COMMAND; echo ") or a malicious event.body (e.g., $(ARBITRARY_COMMAND)) within the function's specification.
3. The Nuclio controller reconciles the malicious NuclioFunction, invoking generateCronTriggerCronJobSpec to construct the internal curl command string.
4. During command construction, the unsanitized headerKey or eventBody is injected directly into the shell command argument passed to /bin/sh -c. For headerKey, double quotes are improperly handled, allowing direct shell command injection; for eventBody, strconv.Quote fails to escape $(...), enabling command substitution.
5. The controller creates a Kubernetes CronJob resource with its container args explicitly configured as /bin/sh -c <malicious_curlCommand>, where malicious_curlCommand now contains the injected arbitrary commands.
6. The Kubernetes scheduler activates the CronJob, causing the CronJob pod to execute the sh -c command, leading to the execution of arbitrary commands (e.g., id, cat /var/run/secrets/...) within the pod. These pods often run with root privileges.
7. The created CronJob lacks Kubernetes ownerReferences, allowing it to persist and continue executing its schedule indefinitely, even if the original NuclioFunction or its Deployment is subsequently removed.
8. The attacker leverages this RCE to exfiltrate sensitive data (such as Kubernetes service account tokens), establish a persistent foothold, or further compromise the Kubernetes cluster.

Impact

Successful exploitation of this vulnerability grants remote attackers persistent remote code execution within the target Kubernetes cluster, typically with root privileges. This allows for arbitrary command execution, sensitive data exfiltration (e.g., Kubernetes service account tokens), and potential for broader compromise of cluster resources. The lack of ownerReferences on the created CronJobs means that even if a compromised NuclioFunction is deleted, the malicious CronJob can continue to run indefinitely, ensuring persistence for the attacker. The vulnerability carries a CVSS 3.1 score of 9.9 (Critical), indicating severe consequences for confidentiality, integrity, and availability of the affected system.

Recommendation

• Patch CVE-XXXX-YYYY immediately: Upgrade Nuclio to a patched version once available. Monitor official Nuclio channels for security updates addressing GHSA-v5px-423j-pf7p.
• Deploy the Sigma rules in this brief: Implement the Detect Nuclio CronJob RCE via Header Key Injection and Detect Nuclio CronJob RCE via Body Command Substitution rules to identify attempts at exploiting this vulnerability at the Kubernetes API server audit log level.
• Review Kubernetes audit logs: Actively monitor for suspicious create, update, or patch events on batch/v1/cronjobs resources, especially those originating from the Nuclio controller, for args fields containing the patterns identified in the IOCs.
• Restrict NuclioFunction deployment permissions: Limit permissions to create or modify NuclioFunction resources to trusted administrators, reducing the attack surface for this vulnerability.