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.
Workaround:
The product does not properly control the allocation and maintenance of a limited resource.
Link | Tags |
---|---|
https://access.redhat.com/security/cve/CVE-2024-25132 | vdb entry |
https://bugzilla.redhat.com/show_bug.cgi?id=2260371 | issue tracking |