fkie_cve-2025-20232
Vulnerability from fkie_nvd
Published
2025-03-26 22:15
Modified
2025-03-27 16:45
Severity ?
5.7 (Medium) - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N
Summary
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.
References
psirt@cisco.comhttps://advisory.splunk.com/advisories/SVD-2025-0304
Impacted products
Vendor Product Version


To clipboard 

{
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "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.",
      },
      {
         lang: "es",
         value: "En las versiones de Splunk Enterprise anteriores a 9.3.3, 9.2.5 y 9.1.8, y de Splunk Cloud Platform anteriores a 9.3.2408.103, 9.2.2406.108, 9.2.2403.113, 9.1.2312.208 y 9.1.2308.212, un usuario con pocos privilegios que no tenga los roles \"admin\" o \"power\" de Splunk podría ejecutar una búsqueda guardada con un comando arriesgado utilizando los permisos de un usuario con más privilegios para eludir las protecciones de SPL para comandos arriesgados en el endpoint \"/app/search/search\" a través de su parámetro \"s\". <br>La vulnerabilidad requiere que el atacante suplante a la víctima, engañándola para que inicie una solicitud en su navegador. El usuario autenticado no debería poder explotar la vulnerabilidad a voluntad.",
      },
   ],
   id: "CVE-2025-20232",
   lastModified: "2025-03-27T16:45:27.850",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "NONE",
               baseScore: 5.7,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "HIGH",
               integrityImpact: "NONE",
               privilegesRequired: "LOW",
               scope: "UNCHANGED",
               userInteraction: "REQUIRED",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N",
               version: "3.1",
            },
            exploitabilityScore: 2.1,
            impactScore: 3.6,
            source: "psirt@cisco.com",
            type: "Primary",
         },
      ],
   },
   published: "2025-03-26T22:15:15.233",
   references: [
      {
         source: "psirt@cisco.com",
         url: "https://advisory.splunk.com/advisories/SVD-2025-0304",
      },
   ],
   sourceIdentifier: "psirt@cisco.com",
   vulnStatus: "Awaiting Analysis",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-200",
            },
         ],
         source: "psirt@cisco.com",
         type: "Primary",
      },
   ],
}


Log in or create an account to share your comment.

Security Advisory comment format.

This schema specifies the format of a comment related to a security advisory.

UUIDv4 of the comment
UUIDv4 of the Vulnerability-Lookup instance
When the comment was created originally
When the comment was last updated
Title of the comment
Description of the comment
The identifier of the vulnerability (CVE ID, GHSA-ID, PYSEC ID, etc.).



Tags
Taxonomy of the tags.




Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
  • Confirmed: The vulnerability is confirmed from an analyst perspective.
  • Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
  • Patched: This vulnerability was successfully patched by the user reporting the sighting.
  • Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
  • Not confirmed: The user expresses doubt about the veracity of the vulnerability.
  • Not patched: This vulnerability was not successfully patched by the user reporting the sighting.