{"answers":{"affected":"2 open source packages ship an affected version, including kibana and elk. It affects 1 product.","exploited":"There is no known exploitation of CVE-2024-52972 in the wild and no public exploit code.","fix":"Upgrade kibana to a fixed version for your release line: 7.17.23 or 8.15.0.","what":"CVE-2024-52972 is a medium-severity denial of service vulnerability in Elastic Kibana, published on 23 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-52972 and fix it if it is affected.\n\nWhat it is: CVE-2024-52972 is a medium-severity denial of service vulnerability in Elastic Kibana, published on 23 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-52972 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- kibana (Bitnami): affected from 7.0.0; fixed in 7.17.23, 8.15.0\n- elk (Bitnami): affected from 7.0.0; fixed in 7.17.23, 8.15.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-52972/ (Markdown: https://insights.sbomify.com/CVE-2024-52972/index.md)","id":"CVE-2024-52972","markdown":"https://insights.sbomify.com/CVE-2024-52972/index.md","name":"CVE-2024-52972","record":{"aliases":["BIT-elk-2024-52972","BIT-kibana-2024-52972","GHSA-28hq-v755-x5ph"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Kibana observability tool","requires_auth":"low_privilege","summary":"Authenticated users with read access can crash Kibana by sending specially crafted requests to the metrics snapshot API.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"kibana","vendor":"elastic"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"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.","ecosystems":["Bitnami"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Kibana allocation of resources without limits or throttling leads to crash","id":"CVE-2024-52972","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Bitnami","product":"elastic:kibana","products":["elastic:kibana"],"type":"denial_of_service","year":"2024"},"n_packages":2,"n_references":1,"next":{"headline":"Kibana allocation of resources without limits or throttling leads to crash","id":"CVE-2024-52973"},"packages":[{"ecosystem":"Bitnami","fixed":["7.17.23","8.15.0"],"introduced":["7.0.0","8.0.0"],"last_affected":[],"package":"elk","purl":"pkg:bitnami/elk","source":"BIT-elk-2024-52972"},{"ecosystem":"Bitnami","fixed":["7.17.23","8.15.0"],"introduced":["7.0.0","8.0.0"],"last_affected":[],"package":"kibana","purl":"pkg:bitnami/kibana","source":"BIT-kibana-2024-52972"}],"prev":{"headline":"SQL injection in FortiSIEM","id":"CVE-2024-52969"},"products":["Kibana"],"published":"2025-01-23","related":[{"cvss_score":9.8,"headline":"Kibana Arbitrary Code Execution","id":"CVE-2019-7609","kev_date_added":"2022-01-10","published":"2019-03-25"},{"cvss_score":9.9,"headline":"Kibana arbitrary code execution via prototype pollution","id":"CVE-2025-25015","kev_date_added":null,"published":"2025-03-05"},{"cvss_score":9.9,"headline":"Deserialization in Kibana","id":"CVE-2024-37288","kev_date_added":null,"published":"2024-09-09"},{"cvss_score":9.9,"headline":"Code injection in Kibana","id":"CVE-2023-31415","kev_date_added":null,"published":"2023-05-04"},{"cvss_score":9.8,"headline":"Information disclosure in Kibana","id":"CVE-2018-17245","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":9.8,"headline":"Code injection in Kibana","id":"CVE-2018-17246","kev_date_added":null,"published":"2018-12-20"},{"cvss_score":9.1,"headline":"Kibana arbitrary code execution via prototype pollution","id":"CVE-2025-25014","kev_date_added":null,"published":"2025-05-06"}],"sources":[{"class":"attribution","licence":"Apache-2.0","name":"Bitnami","prefix":"BIT"},{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-23","vendors":["Elastic"]},"summary":"Authenticated users with read access can crash Kibana by sending specially crafted requests to the metrics snapshot API.","url":"https://insights.sbomify.com/CVE-2024-52972/"}