In Splunk Enterprise versions below 10.4.5, 10.2.9, 10.0.12, and 9.4.17, an unauthenticated user could use an empty clustering shared secret to read and modify clustering configuration through the cluster configuration Representational State Transfer (REST) API endpoint on a standalone instance. This could expose clustering configuration, persist attacker-controlled clustering settings, and disrupt clustering operations.
The vulnerability is possible because Splunk Enterprise accepts the empty clustering shared secret as a shared-authentication candidate on a standalone instance when clustering is turned off.
If you cannot immediately upgrade to a fixed version, set a strong, unique pass4SymmKey value in the [clustering] stanza in the server.conf configuration file, including on standalone instances. The pass4SymmKey value must contain at least 12 characters. The file is at etc/system/local/server.conf under the Splunk Enterprise installation directory. Restart Splunk Enterprise for the change to take effect.
For more information see Secure Splunk Enterprise services with pass4SymmKey in the Splunk documentation.
Upgrade Splunk Enterprise versions 10.6.1, 10.4.5, 10.2.9, 10.0.12, and 9.4.17 or higher.