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)

#%NASL_MIN_LEVEL 80900
##
# (C) Tenable, Inc.
##

include('compat.inc');

if (description)
{
  script_id(241440);
  script_version("1.3");
  script_set_attribute(attribute:"plugin_modification_date", value:"2026/01/21");

  script_cve_id("CVE-2025-20325");
  script_xref(name:"IAVA", value:"2025-A-0502-S");

  script_name(english:"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)");

  script_set_attribute(attribute:"synopsis", value:
"An application running on a remote web server host is affected by a vulnerability");
  script_set_attribute(attribute:"description", value:
"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.");
  script_set_attribute(attribute:"see_also", value:"https://advisory.splunk.com/advisories/SVD-2025-0709.html");
  script_set_attribute(attribute:"solution", value:
"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.");
  script_set_attribute(attribute:"agent", value:"all");
  script_set_cvss_base_vector("CVSS2#AV:N/AC:H/Au:S/C:P/I:N/A:N");
  script_set_cvss_temporal_vector("CVSS2#E:U/RL:OF/RC:C");
  script_set_cvss3_base_vector("CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N");
  script_set_cvss3_temporal_vector("CVSS:3.0/E:U/RL:O/RC:C");
  script_set_attribute(attribute:"cvss_score_source", value:"CVE-2025-20325");

  script_set_attribute(attribute:"exploitability_ease", value:"No known exploits are available");
  script_set_attribute(attribute:"exploit_available", value:"false");
  script_cwe_id(200);

  script_set_attribute(attribute:"vuln_publication_date", value:"2025/07/07");
  script_set_attribute(attribute:"patch_publication_date", value:"2025/07/07");
  script_set_attribute(attribute:"plugin_publication_date", value:"2025/07/07");

  script_set_attribute(attribute:"potential_vulnerability", value:"true");
  script_set_attribute(attribute:"plugin_type", value:"combined");
  script_set_attribute(attribute:"cpe", value:"cpe:/a:splunk:splunk");
  script_set_attribute(attribute:"generated_plugin", value:"current");
  script_set_attribute(attribute:"stig_severity", value:"I");
  script_end_attributes();

  script_category(ACT_GATHER_INFO);
  script_family(english:"CGI abuses");

  script_copyright(english:"This script is Copyright (C) 2025-2026 and is owned by Tenable, Inc. or an Affiliate thereof.");

  script_dependencies("splunkd_detect.nasl", "splunk_web_detect.nasl", "macos_splunk_installed.nbin", "splunk_win_installed.nbin", "splunk_nix_installed.nbin");
  script_require_keys("installed_sw/Splunk", "Settings/ParanoidReport");

  exit(0);
}

include('vcf.inc');
include('vcf_extras_splunk.inc');

if (report_paranoia < 2) audit(AUDIT_PARANOID);

var app_info = vcf::splunk::get_app_info();

var constraints = [
  { 'min_version' : '9.1.0', 'fixed_version' : '9.1.10', 'license' : 'Enterprise' },
  { 'min_version' : '9.2.0', 'fixed_version' : '9.2.7', 'license' : 'Enterprise' },
  { 'min_version' : '9.3.0', 'fixed_version' : '9.3.5', 'license' : 'Enterprise' },
  { 'min_version' : '9.4.0', 'fixed_version' : '9.4.3', 'license' : 'Enterprise' }
];
vcf::splunk::check_version_and_report(
    app_info:app_info,
    constraints:constraints,
    severity:SECURITY_NOTE
);