Details
Check HTTP server logs (shows WASM download):
172.18.0.2 - - [01/Feb/2026 21:55:58] "GET /malicious.wasm HTTP/1.1" 200 -
172.18.0.2 - - [01/Feb/2026 21:56:32] "GET /malicious.wasm HTTP/1.1" 200 -
172.18.0.2 - - [01/Feb/2026 21:56:33] "GET /malicious.wasm HTTP/1.1" 200 -
Check created ConfigMap:
kubectl get configmap stolen-credentials -n default -o yaml
Actual output from verification:
apiVersion: v1
kind: ConfigMap
metadata:
name: stolen-credentials
namespace: default
labels:
vulnerability: VUL-001
type: exfiltrated-token
app.kubernetes.io/managed-by: atc.yoke
instance.atc.yoke.cd/name: malicious-backend-v2
data:
vulnerability: 'VUL-001: AnnotationOverrideFlight Injection allows arbitrary WASM execution'
Expected Result
The malicious WASM module is downloaded and executed by the ATC controller, creating a ConfigMap named stolen-credentials in the cluster. This proves arbitrary code execution in the ATC controller context.
Impact
Vulnerability Type: Remote Code Execution (RCE) / Code Injection
Attack Prerequisites:
- Attacker has permission to create/update Custom Resources managed by Yoke ATC
- Network access to host malicious WASM (can be external URL)
Impact Assessment:
- Confidentiality: High - Attacker can create resources to exfiltrate data; if ClusterAccess is enabled, can read cluster secrets via host functions
- Integrity: High - Attacker can create/modify arbitrary Kubernetes resources through WASM output
- Availability: Medium - Attacker can disrupt cluster operations by creating malicious resources
Attack Scenario:
- CI/CD developer or application developer with CR permissions creates a Backend CR with malicious annotation
- ATC controller downloads and executes attacker-controlled WASM
- Malicious WASM creates backdoor resources or exfiltrates sensitive data
- If ClusterAccess is enabled, attacker can read secrets and escalate to cluster-admin
Severity
CVSS v3.1 Score: 8.8 (High)
Vector: AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Attack Vector (AV): Network - Malicious WASM can be hosted externally
- Attack Complexity (AC): Low - Simple annotation injection
- Privileges Required (PR): Low - Only CR create/update permission needed
- User Interaction (UI): None - Automatic execution on CR creation
- Scope (S): Unchanged - Impact within ATC controller context
- Confidentiality (C): High - Can access controller context data
- Integrity (I): High - Can create arbitrary resources
- Availability (A): High - Can disrupt cluster operations
Affected Versions
- Yoke ATC v0.18.x and earlier versions
- All versions that support the
overrides.yoke.cd/flightannotation
Patched Versions
No patch available at time of disclosure.
Workarounds
- Disable annotation override feature: Remove or disable the
overrides.yoke.cd/flightannotation processing in production environments
- Network policy: Restrict ATC controller's outbound network access to prevent downloading external WASM modules
- RBAC hardening: Limit CR create/update permissions to trusted users only
- Admission webhook: Deploy a validating webhook to reject CRs with
overrides.yoke.cd/flightannotations
References
- Yoke Project: https://github.com/yokecd/yoke
- Yoke ATC Documentation: https://yokecd.github.io/docs/airtrafficcontroller/atc/
- CWE-94: Improper Control of Generation of Code: https://cwe.mitre.org/data/definitions/94.html
Credits
credit for:
@b0b0haha ([email protected])
@lixingquzhi ([email protected])