Red Hat OpenShift v1 spec.hibernateAfter resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.2 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Red Hat OpenShift and classified as problematic. This affects an unknown function of the file ClusterDeployment.hive.OpenShift.io/v1. This manipulation of the argument spec.hibernateAfter causes resource consumption. This vulnerability is handled as CVE-2024-25132. The attack can be initiated remotely. There is not any exploit available. It is suggested to install a patch to address this issue.
Details
A vulnerability was found in Red Hat OpenShift (the affected version unknown). It has been declared as problematic. Affected by this vulnerability is an unknown part of the file ClusterDeployment.hive.OpenShift.io/v1. The manipulation of the argument spec.hibernateAfter with an unknown input leads to a resource consumption vulnerability. The CWE definition for the vulnerability is CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. As an impact it is known to affect availability. The summary by CVE is:
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.
The advisory is shared at access.redhat.com. This vulnerability is known as CVE-2024-25132 since 02/05/2024. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Applying the patch 126c7eb43aa55a008b8f0cf594e7bd18086841eb is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-22481). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
License
Website
- Vendor: https://www.redhat.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.2
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.3
CNA Vector (redhat): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔍
Patch: 126c7eb43aa55a008b8f0cf594e7bd18086841eb
Timeline
02/05/2024 🔍03/19/2025 🔍
03/19/2025 🔍
05/22/2025 🔍
Sources
Vendor: redhat.comAdvisory: access.redhat.com
Status: Confirmed
CVE: CVE-2024-25132 (🔍)
GCVE (CVE): GCVE-0-2024-25132
GCVE (VulDB): GCVE-100-300121
EUVD: 🔍
Entry
Created: 03/19/2025 22:59Updated: 05/22/2025 20:26
Changes: 03/19/2025 22:59 (65), 05/22/2025 20:26 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.