CVE-2025-20230: Missing Access Control and Incorrect Ownership of Data in App Key Value Store (KVStore) collections in the Splunk Secure Gateway App
First published: Wed Mar 26 2025(Updated: )
In Splunk Enterprise versions below 9.4.1, 9.3.3, 9.2.5, and 9.1.8, and versions below 3.8.38 and 3.7.23 of the Splunk Secure Gateway app on Splunk Cloud Platform, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could edit and delete other user data in App Key Value Store (KVStore) collections that the Splunk Secure Gateway app created. This is due to missing access control and incorrect ownership of the data in those KVStore collections.<br><br>In the affected versions, the `nobody` user owned the data in the KVStore collections. This meant that there was no specific owner assigned to the data in those collections.
Credit: psirt@cisco.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Splunk Enterprise | <9.4.1 | |
| Splunk Enterprise | <9.3.3 | |
| Splunk Enterprise | <9.2.5 | |
| Splunk Enterprise | <9.1.8 | |
| Splunk Secure Gateway | <3.8.38 | |
| Splunk Secure Gateway | <3.7.23 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-20230?
CVE-2025-20230 is classified as a moderate severity vulnerability.
How do I fix CVE-2025-20230?
To fix CVE-2025-20230, upgrade to Splunk Enterprise version 9.4.1 or later, or the latest versions of the Splunk Secure Gateway app.
Who is affected by CVE-2025-20230?
Users of Splunk Enterprise versions below 9.4.1 and those using outdated Splunk Secure Gateway app versions are affected by CVE-2025-20230.
What impact does CVE-2025-20230 have on user data?
CVE-2025-20230 allows low-privileged users to edit and delete data belonging to other users.
Is there a workaround for CVE-2025-20230?
There are no known workarounds for CVE-2025-20230; upgrading to the secure versions is the recommended approach.
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/title
- agent/weakness
- agent/type
- agent/description
- agent/first-publish-date
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/last-modified-date
- agent/severity
- agent/author
- agent/source
- agent/event
- agent/tags
- agent/guess-ai
- agent/software-canonical-lookup
- vendor/splunk
- canonical/splunk enterprise
- canonical/splunk secure gateway