{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2024-36986 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2024-36986 yet. Limit exposure of the affected software until one is available.","what":"CVE-2024-36986 is a medium-severity vulnerability in Splunk Splunk, published on 1 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2024-36986 and fix it if it is affected.\n\nWhat it is: CVE-2024-36986 is a medium-severity vulnerability in Splunk Splunk, published on 1 Jul 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2024-36986 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-36986/ (Markdown: https://insights.sbomify.com/CVE-2024-36986/index.md)","id":"CVE-2024-36986","markdown":"https://insights.sbomify.com/CVE-2024-36986/index.md","name":"CVE-2024-36986","record":{"aliases":["GHSA-xgxh-897r-pw22"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Splunk Enterprise","requires_auth":"low_privilege","summary":"Authenticated users can bypass SPL safeguards to execute risky commands with higher privileges via phishing in Splunk Analytics Workspace.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Splunk","cpe":[{"product":"cloud","vendor":"splunk"},{"product":"splunk","vendor":"splunk"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"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.200 and 9.1.2308.207, an authenticated user could run risky commands using the permissions of a higher-privileged user to bypass SPL safeguards for risky commands in the Analytics Workspace. The vulnerability requires the authenticated user to phish the victim by tricking them into initiating a request within their browser. The authenticated user should not be able to exploit the vulnerability at will.","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":"Risky command safeguards bypass through Search ID query in Analytics Workspace","id":"CVE-2024-36986","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"splunk:splunk","products":["splunk:splunk"],"type":"security_feature_bypass","year":"2024"},"n_packages":0,"n_references":2,"next":{"headline":"Insecure File Upload in the indexing/preview REST endpoint","id":"CVE-2024-36987"},"packages":[],"prev":{"headline":"Code injection in Splunk Enterprise","id":"CVE-2024-36985"},"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":7.5,"headline":"Denial of Service through null pointer reference in “cluster/config” REST endpoint","id":"CVE-2024-36982","kev_date_added":null,"published":"2024-07-01"},{"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":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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-28","vendors":["Splunk"]},"summary":"Authenticated users can bypass SPL safeguards to execute risky commands with higher privileges via phishing in Splunk Analytics Workspace.","url":"https://insights.sbomify.com/CVE-2024-36986/"}