Skip to content
Fencer Intel
medium 6.5

CVE-2024-52972 json

Kibana allocation of resources without limits or throttling leads to crash

published last yr. modified 2mo ago also BIT-elk-2024-52972 , BIT-kibana-2024-52972 , EUVD-2024-46265

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 34%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami elk 7.17.23, 8.15.0
  • bitnami kibana 7.17.23, 8.15.0
  • Elastic Kibana 7.17.23, 8.15.0

Is CVE-2024-52972 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.40% chance of exploitation in the next 30 days, higher than 34% of all scored CVEs (FIRST EPSS, 2026-11-11).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
bitnami elk
>=7.0.0, <7.17.23
>=8.0.0, <8.15.0
7.17.23
8.15.0
bitnami kibana
>=7.0.0, <7.17.23
>=8.0.0, <8.15.0
7.17.23
8.15.0

Affected products

  • Elastic Kibana

Classification

Weakness
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.