Filtered by vendor Splunk Subscriptions
Filtered by product Splunk Enterprise Subscriptions
Total 45 CVE
CVE Vendors Products Updated CVSS v3.1
CVE-2024-36982 1 Splunk 4 Cloud, Splunk, Splunk Cloud Platform and 1 more 2025-02-28 7.5 High
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.
CVE-2024-45731 2 Microsoft, Splunk 3 Windows, Splunk, Splunk Enterprise 2025-02-28 8 High
In Splunk Enterprise for Windows versions below 9.3.1, 9.2.3, and 9.1.6, a low-privileged user that does not hold the "admin" or "power" Splunk roles could write a file to the Windows system root directory, which has a default location in the Windows System32 folder, when Splunk Enterprise for Windows is installed on a separate drive.
CVE-2024-45733 2 Microsoft, Splunk 3 Windows, Splunk, Splunk Enterprise 2025-02-28 8.8 High
In Splunk Enterprise for Windows versions below 9.2.3 and 9.1.6, a low-privileged user that does not hold the "admin" or "power" Splunk roles could perform a Remote Code Execution (RCE) due to an insecure session storage configuration.
CVE-2024-45734 1 Splunk 2 Splunk, Splunk Enterprise 2025-02-28 4.3 Medium
In Splunk Enterprise versions 9.3.0, 9.2.3, and 9.1.6, a low-privileged user that does not hold the "admin" or "power" Splunk roles could view images on the machine that runs Splunk Enterprise by using the PDF export feature in Splunk classic dashboards. The images on the machine could be exposed by exporting the dashboard as a PDF, using the local image path in the img tag in the source extensible markup language (XML) code for the Splunk classic dashboard.
CVE-2024-36996 1 Splunk 3 Splunk, Splunk Cloud Platform, Splunk Enterprise 2025-02-28 5.3 Medium
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, an attacker could determine whether or not another user exists on the instance by deciphering the error response that they would likely receive from the instance when they attempt to log in. This disclosure could then lead to additional brute-force password-guessing attacks. This vulnerability would require that the Splunk platform instance uses the Security Assertion Markup Language (SAML) authentication scheme.