Apache YuniKorn vulnerabilities

Apache YuniKorn 1.9.0 and earlier allows bypassing the check for the user annotation by setting a secondary label on the pod. If the pod has the label 'app=yunikorn' the checks limiting the user annotation content are not run. The label is used to identify the YuniKorn application itself in the deployments. The bypass allows any user to specify an arbitrary user info annotation. The arbitrary user information 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.

Apache YuniKorn up to 1.9.0 does not enforce label and user annotation checks for workload UPDATE actions, bypassing all checks. This allows any user to set arbitrary user annotations and change the application ID, potentially gaining access to queues they normally cannot access. Upgrade to version 1.10.0 is recommended.

Apache YuniKorn 1.8.0 and later, when configured with the LDAP group resolver, crashes due to an out-of-bounds read processing group membership entries. If the LDAP server returns a memberOf attribute for a user and the record does not start with "CN=", the server crashes. This only affects installations with the non-default LDAP group provider. Upgrade to version 1.10.0 is recommended.