A flaw was found in the Hive hibernation controller component of OpenShift Dedicated. The ClusterDeployment.hive.openshift.io/v1 resource can be created with the spec.installed field set to true, regardless of the installation status, and a positive timespan for the spec.hibernateAfter value. If a ClusterSync.hiveinternal.openshift.io/v1alpha1 resource is also created, the hive hibernation controller will enter the reconciliation loop leading to a panic when accessing a non-existing field in the ClusterDeployment’s status section, resulting in a denial of service.
{ "nvd_published_at": "2025-03-19T18:15:20Z", "github_reviewed": true, "github_reviewed_at": "2025-03-20T13:18:17Z", "severity": "MODERATE", "cwe_ids": [ "CWE-400" ] }