{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2024-36982 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-36982 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-36982 is a high-severity vulnerability in Splunk Splunk, published on 1 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-36982 and fix it if it is affected.\n\nWhat it is: CVE-2024-36982 is a high-severity vulnerability in Splunk Splunk, published on 1 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-36982 in the wild and no public exploit code.\n\nAffected product: Splunk Splunk. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-36982/ (Markdown: https://insights.sbomify.com/CVE-2024-36982/index.md)","id":"CVE-2024-36982","markdown":"https://insights.sbomify.com/CVE-2024-36982/index.md","name":"CVE-2024-36982","record":{"aliases":["GHSA-2m84-pxgc-c9vw"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Enterprise","requires_auth":"none","summary":"An attacker can crash the Splunk daemon via a null pointer dereference in the cluster/config REST endpoint, causing denial of service.","user_interaction":"not_required","vuln_class":"null_dereference"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Splunk","cpe":[{"product":"cloud","vendor":"splunk"},{"product":"splunk","vendor":"splunk"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-476","name":"NULL Pointer Dereference"}],"description":"In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.109 and 9.1.2308.207, an attacker could trigger a null pointer reference on the cluster/config REST endpoint, which could result in a crash of the Splunk daemon.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Denial of Service through null pointer reference in “cluster/config” REST endpoint","id":"CVE-2024-36982","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk"],"type":"null_dereference","year":"2024"},"n_packages":0,"n_references":1,"next":{"headline":"Command Injection using External Lookups","id":"CVE-2024-36983"},"packages":[],"prev":{"headline":"Denial of service in OpenPLC v3","id":"CVE-2024-36981"},"products":["Splunk Cloud Platform","Splunk Enterprise"],"published":"2024-07-01","related":[{"cvss_score":8,"headline":"Remote code execution (RCE) in Splunk Enterprise through Insecure XML Parsing","id":"CVE-2023-46214","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":6.5,"headline":"Low-privileged user could create notifications in Splunk Web Bulletin Messages","id":"CVE-2024-36989","kev_date_added":null,"published":"2024-07-01"},{"cvss_score":6.5,"headline":"Splunk App Key Value Store (KV Store) Improper Handling of Permissions Leads to KV Store Collection Deletion","id":"CVE-2024-23675","kev_date_added":null,"published":"2024-01-22"},{"cvss_score":6.3,"headline":"Risky command safeguards bypass through Search ID query in Analytics Workspace","id":"CVE-2024-36986","kev_date_added":null,"published":"2024-07-01"},{"cvss_score":4.8,"headline":"Cross-site Scripting (XSS) on “Show Syntax Highlighted” View in Search Page","id":"CVE-2023-46213","kev_date_added":null,"published":"2023-11-16"},{"cvss_score":4.6,"headline":"Sensitive Information Disclosure of Index Metrics through “mrollup” SPL Command","id":"CVE-2024-23676","kev_date_added":null,"published":"2024-01-22"}],"sources":[{"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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-28","vendors":["Splunk"]},"summary":"An attacker can crash the Splunk daemon via a null pointer dereference in the cluster/config REST endpoint, causing denial of service.","url":"https://insights.sbomify.com/CVE-2024-36982/"}