Detections
Analytics

Splunk Enterprise 9.1.0 < 9.1.10, 9.2.0 < 9.2.7, 9.3.0 < 9.3.5, 9.4.0 < 9.4.3 (SVD-2025-0709)

low Nessus Plugin ID 241440

Language:

Synopsis

An application running on a remote web server host is affected by a vulnerability

Description

The version of Splunk installed on the remote host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the SVD-2025-0709 advisory.

 - In Splunk Enterprise versions below 9.4.3, 9.3.5, 9.2.7, and 9.1.10, and Splunk Cloud Platform versions below 9.3.2411.103, 9.3.2408.113, and 9.2.2406.119, the software potentially exposes the search head cluster splunk.secret key. This exposure could happen if you have a Search Head cluster and you configure the Splunk Enterprise SHCConfig log channel at the DEBUG logging level in the clustered deployment. The vulnerability would require either local access to the log files or administrative access to internal indexes, which by default only the admin role receives. Review roles and capabilities on your instance and restrict internal index access to administrator-level roles. See Define roles on the Splunk platform with capabilities, Deploy a search head cluster, Deploy secure passwords across multiple servers and Set a security key for the search head cluster for more information. (CVE-2025-20325)

Note that Nessus has not tested for this issue but has instead relied only on the application's self-reported version number.

Solution

There are multiple solutions depending on how you have configured the Splunk Enterprise instance SHCConfig log channel.First, determine whether or not you have a Search Head cluster. If you have a Search Head cluster, determine whether or not the SHCConfig log channel is at the DEBUG logging level. You must log into the Splunk Enterprise instance as an admin user or equivalent to perform these actions. To determine the log channel logging mode on the instance: 1.
In a web browser, visit the Server Logging Settings page in Splunk Web at /en-US/manager/system/server/logger. 2. Review the Logging Level column on the page that loads. If the SHCConfig row in this column shows DEBUG as the logging level, then the Splunk Enterprise SHCConfig log channel is in debug mode. Otherwise, it is not in debug mode.See Enable debug logging for more information.If the previous steps determine that debug logging is active for theSHCConfiglog channel, then remedy the problem by performing the following tasks:1. Upgrade Splunk Enterprise to versions 9.4.3, 9.3.5, 9.2.7, and 9.1.10, or higher.2. Update the splunk.secret key file. See Update the splunk.secret key file on instances to use the new cipher for more information.Splunk is actively monitoring and patching Splunk Cloud Platform instances.

See Also

https://advisory.splunk.com/advisories/SVD-2025-0709.html

Plugin Details

Severity: Low

ID: 241440

File Name: splunk_943_cve-2025-20325.nasl

Version: 1.2

Type: combined

Agent: windows, macosx, unix

Family: CGI abuses

Published: 7/7/2025

Updated: 7/11/2025

Configuration: Enable paranoid mode

Supported Sensors: Nessus Agent, Nessus

Risk Information

VPR

Risk Factor: Low

Score: 3.9

CVSS v2

Risk Factor: Low

Base Score: 2.1

Temporal Score: 1.6

Vector: CVSS2#AV:N/AC:H/Au:S/C:P/I:N/A:N

CVSS Score Source: CVE-2025-20325

CVSS v3

Risk Factor: Low

Base Score: 3.1

Temporal Score: 2.7

Vector: CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C

Vulnerability Information

CPE: cpe:/a:splunk:splunk

Required KB Items: Settings/ParanoidReport, installed_sw/Splunk

Exploit Ease: No known exploits are available

Patch Publication Date: 7/7/2025

Vulnerability Publication Date: 7/7/2025

Reference Information

CVE: CVE-2025-20325

CWE: 200

IAVA: 2025-A-0502