CyberRota Analysis
AI-GeneratedApache YuniKorn versions 1.9.0 and earlier are vulnerable due to a lack of proper checks during workload UPDATE actions, allowing users to bypass restrictions and modify user info annotations and application IDs. This could lead to unauthorized access to queues and potential quota misuse, impacting resource allocation and management. Organizations using Apache YuniKorn in conjunction with Kubernetes should prioritize upgrading to version 1.10.0 to mitigate these risks.
Original NVD Description
Apache YuniKorn 1.9.0 and earlier does not implement label and user annotation checks for workload UPDATE action bypassing all checks. Workloads in YuniKorn are defined as the following Kubernetes objects: "deployments", "replicasets", "statefulsets", "daemonsets", "jobs", "cronjobs". The CREATE action correctly enforces the checks for all object types. The bypass allows any user to specify an arbitrary user info annotation. The same bypass also allows changing the application ID for the workload. The combination of the two applied in one UPDATE could allow access to a queue that the user normally would not have access to. Quota usage for the queue might be impacted if the application runs in the incorrect queue. User based quota enforcement is also based on the user annotation. User quota tracking could be side stepped even if the application runs in the correct queue. Users are recommended to upgrade to version 1.10.0, which fixes this issue.