First published: Mon Oct 14 2024(Updated: )
In Splunk Enterprise versions below 9.3.1, and 9.2.0 versions below 9.2.3, and Splunk Cloud Platform versions below 9.2.2403.103, 9.1.2312.200, 9.1.2312.110 and 9.1.2308.208, a low-privileged user that does not hold the "admin" or "power" Splunk roles could run a search as the "nobody" Splunk user in the SplunkDeploymentServerConfig app. This could let the low-privileged user access potentially restricted data.
Credit: prodsec@splunk.com
Affected Software | Affected Version | How to fix |
---|---|---|
Splunk Splunk | >=9.2.0<9.2.3 | |
Splunk Splunk | =9.3.0 | |
Splunk Cloud Platform | <9.1.2308.208 | |
Splunk Cloud Platform | >=9.1.2312.100<9.1.2312.110 | |
Splunk Cloud Platform | >=9.2.2403.102<9.2.2403.103 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2024-45732 is considered a low-severity vulnerability affecting specific Splunk versions.
To resolve CVE-2024-45732, upgrade your Splunk Enterprise or Splunk Cloud Platform to the latest version specified in the advisory.
CVE-2024-45732 affects Splunk Enterprise versions below 9.3.1 and 9.2.0 below 9.2.3, as well as specific Splunk Cloud Platform versions.
CVE-2024-45732 can be exploited by low-privileged users who do not hold the 'admin' or 'power' roles in Splunk.
Yes, patches for CVE-2024-45732 are included in the latest releases of the affected Splunk versions.