CVE-2025-20232
Essential information
- Published
- 26/03/2025 22:15
- Modified
- 27/03/2025 16:45
- Author
- —
- Creator
- —
- CVSS
- 5.7 MEDIUM (v3.1)
- CISA KEV
- No
- CWE
- —
- CVSS vector
-
—
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N—
CVSS metrics
- Access vector
- —
- Access complexity
- —
- Authentication
- —
- Confidentiality impact
- —
- Integrity impact
- —
- Availability impact
- —
- Exploitability
- —
- Remediation level
- —
- Report confidence
- —
- Temporal score
- —
- Attack vector
- NETWORK
- Attack complexity
- LOW
- Privileges required
- LOW
- User interaction
- REQUIRED
- Scope
- UNCHANGED
- Confidentiality impact
- HIGH
- Integrity impact
- NONE
- Availability impact
- NONE
- Exploit code maturity
- —
- Remediation level
- —
- Report confidence
- —
- Temporal score
- —
- Attack vector
- —
- Attack complexity
- —
- Attack requirements
- —
- Privileges required
- —
- User interaction
- —
- Confidentiality (V)
- —
- Confidentiality (S)
- —
- Integrity (V)
- —
- Integrity (S)
- —
- Availability (V)
- —
- Availability (S)
- —
- Exploit maturity
- —
Description
In Splunk Enterprise versions below 9.3.3, 9.2.5, and 9.1.8 and Splunk Cloud Platform versions below 9.3.2408.103, 9.2.2406.108, 9.2.2403.113, 9.1.2312.208 and 9.1.2308.212, a low-privileged user that does not hold the “admin“ or “power“ Splunk roles could run a saved search with a risky command using the permissions of a higher-privileged user to bypass the SPL safeguards for risky commands on the “/app/search/search“ endpoint through its “s“ parameter. <br>The vulnerability requires the attacker 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.
NVD status
- Status
- Awaiting Analysis — CVE has been recently published to the CVE List and has been received by the NVD.
- Source
- [email protected]
- NVD
- View on NVD
Affected products (CPE)
| Product | CPE |
|---|---|
| splunk / splunk enterprise | cpe:2.3:a:splunk:splunk_enterprise:<9.3.3:*:*:*:*:*:*:* |
| splunk / splunk enterprise | cpe:2.3:a:splunk:splunk_enterprise:<9.2.5:*:*:*:*:*:*:* |
| splunk / splunk enterprise | cpe:2.3:a:splunk:splunk_enterprise:<9.1.8:*:*:*:*:*:*:* |
| splunk / splunk cloud platform | cpe:2.3:a:splunk:splunk_cloud_platform:<9.3.2408.103:*:*:*:*:*:*:* |
| splunk / splunk cloud platform | cpe:2.3:a:splunk:splunk_cloud_platform:<9.2.2406.108:*:*:*:*:*:*:* |
| splunk / splunk cloud platform | cpe:2.3:a:splunk:splunk_cloud_platform:<9.2.2403.113:*:*:*:*:*:*:* |
| splunk / splunk cloud platform | cpe:2.3:a:splunk:splunk_cloud_platform:<9.1.2312.208:*:*:*:*:*:*:* |
| splunk / splunk cloud platform | cpe:2.3:a:splunk:splunk_cloud_platform:<9.1.2308.212:*:*:*:*:*:*:* |