Elastic Kibana up to 7.17.22/8.14.x Request /api/metrics/snapshot allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Elastic Kibana up to 7.17.22/8.14.x. Affected by this issue is some unknown functionality of the file /api/metrics/snapshot of the component Request Handler. The manipulation leads to allocation of resources. This vulnerability is traded as CVE-2024-52972. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in Elastic Kibana up to 7.17.22/8.14.x. It has been rated as critical. This issue affects an unknown code of the file /api/metrics/snapshot of the component Request Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability. The summary by CVE is:
An allocation of resources without limits or throttling in Kibana can lead to a crash caused by a specially crafted request to /api/metrics/snapshot. This can be carried out by users with read access to the Observability Metrics or Logs features in Kibana.
The advisory is shared at discuss.elastic.co. The identification of this vulnerability is CVE-2024-52972 since 11/18/2024. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 7.17.23 or 8.15.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 7.17.0
- 7.17.1
- 7.17.2
- 7.17.3
- 7.17.4
- 7.17.5
- 7.17.6
- 7.17.7
- 7.17.8
- 7.17.9
- 7.17.10
- 7.17.11
- 7.17.12
- 7.17.13
- 7.17.14
- 7.17.15
- 7.17.16
- 7.17.17
- 7.17.18
- 7.17.19
- 7.17.20
- 7.17.21
- 7.17.22
- 8.0
- 8.1
- 8.2
- 8.3
- 8.4
- 8.5
- 8.6
- 8.7
- 8.8
- 8.9
- 8.10
- 8.11
- 8.12
- 8.13
- 8.14
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.5VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.5
VulDB Temp Score: 6.2
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.5
CNA Vector (elastic): 🔍
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: Allocation of resourcesCWE: CWE-770 / 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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Kibana 7.17.23/8.15.0
Timeline
11/18/2024 🔍01/23/2025 🔍
01/23/2025 🔍
01/23/2025 🔍
Sources
Advisory: discuss.elastic.coStatus: Confirmed
CVE: CVE-2024-52972 (🔍)
GCVE (CVE): GCVE-0-2024-52972
GCVE (VulDB): GCVE-100-293129
Entry
Created: 01/23/2025 07:33Updated: 01/23/2025 15:18
Changes: 01/23/2025 07:33 (64), 01/23/2025 15:18 (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.