fkie_cve-2024-36983
Vulnerability from fkie_nvd
Published
2024-07-01 17:15
Modified
2025-03-07 17:13
Severity ?
8.0 (High) - CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
8.8 (High) - CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Summary
In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.109 and 9.1.2308.207, an authenticated user could create an external lookup that calls a legacy internal function. The authenticated user could use this internal function to insert code into the Splunk platform installation directory. From there, the user could execute arbitrary code on the Splunk platform Instance.
References
prodsec@splunk.comhttps://advisory.splunk.com/advisories/SVD-2024-0703Vendor Advisory
prodsec@splunk.comhttps://research.splunk.com/application/1cf58ae1-9177-40b8-a26c-8966040f11ae/Tool Signature
af854a3a-2127-422b-91ae-364da2661108https://advisory.splunk.com/advisories/SVD-2024-0703Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://research.splunk.com/application/1cf58ae1-9177-40b8-a26c-8966040f11ae/Tool Signature
Impacted products
Vendor Product Version
splunk splunk *
splunk splunk *
splunk splunk *
splunk splunk_cloud_platform *
splunk splunk_cloud_platform *


To clipboard 

{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*",
                     matchCriteriaId: "09264EE5-FA8A-49C5-AB1F-AEAC16CDC591",
                     versionEndExcluding: "9.0.10",
                     versionStartIncluding: "9.0.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*",
                     matchCriteriaId: "565039EE-74F6-451C-AFB3-F6C9F7AA0EEE",
                     versionEndExcluding: "9.1.5",
                     versionStartIncluding: "9.1.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*",
                     matchCriteriaId: "B1342052-4733-49BB-95F0-A89B07A3F2E3",
                     versionEndExcluding: "9.2.2",
                     versionStartIncluding: "9.2.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "D220E842-2B15-416F-960B-397166883F9F",
                     versionEndExcluding: "9.1.2308.207",
                     versionStartIncluding: "9.1.2308",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:splunk:splunk_cloud_platform:*:*:*:*:*:*:*:*",
                     matchCriteriaId: "F2E66C0D-BD3A-46CE-9578-068401F094C0",
                     versionEndExcluding: "9.1.2312.109",
                     versionStartIncluding: "9.1.2312",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "In Splunk Enterprise versions below 9.2.2, 9.1.5, and 9.0.10 and Splunk Cloud Platform versions below 9.1.2312.109 and 9.1.2308.207, an authenticated user could create an external lookup that calls a legacy internal function. The authenticated user could use this internal function to insert code into the Splunk platform installation directory. From there, the user could execute arbitrary code on the Splunk platform Instance.",
      },
      {
         lang: "es",
         value: "En las versiones de Splunk Enterprise inferiores a 9.2.2, 9.1.5 y 9.0.10 y en las versiones de Splunk Cloud Platform inferiores a 9.1.2312.109 y 9.1.2308.207, un usuario autenticado podría crear una búsqueda externa que llame a una función interna heredada. El usuario autenticado podría utilizar esta función interna para insertar código en el directorio de instalación de la plataforma Splunk. Desde allí, el usuario podría ejecutar código arbitrario en la instancia de la plataforma Splunk.",
      },
   ],
   id: "CVE-2024-36983",
   lastModified: "2025-03-07T17:13:55.270",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "HIGH",
               baseScore: 8,
               baseSeverity: "HIGH",
               confidentialityImpact: "HIGH",
               integrityImpact: "HIGH",
               privilegesRequired: "LOW",
               scope: "UNCHANGED",
               userInteraction: "REQUIRED",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H",
               version: "3.1",
            },
            exploitabilityScore: 2.1,
            impactScore: 5.9,
            source: "prodsec@splunk.com",
            type: "Secondary",
         },
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "HIGH",
               baseScore: 8.8,
               baseSeverity: "HIGH",
               confidentialityImpact: "HIGH",
               integrityImpact: "HIGH",
               privilegesRequired: "LOW",
               scope: "UNCHANGED",
               userInteraction: "NONE",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
               version: "3.1",
            },
            exploitabilityScore: 2.8,
            impactScore: 5.9,
            source: "nvd@nist.gov",
            type: "Primary",
         },
      ],
   },
   published: "2024-07-01T17:15:06.257",
   references: [
      {
         source: "prodsec@splunk.com",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://advisory.splunk.com/advisories/SVD-2024-0703",
      },
      {
         source: "prodsec@splunk.com",
         tags: [
            "Tool Signature",
         ],
         url: "https://research.splunk.com/application/1cf58ae1-9177-40b8-a26c-8966040f11ae/",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://advisory.splunk.com/advisories/SVD-2024-0703",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Tool Signature",
         ],
         url: "https://research.splunk.com/application/1cf58ae1-9177-40b8-a26c-8966040f11ae/",
      },
   ],
   sourceIdentifier: "prodsec@splunk.com",
   vulnStatus: "Analyzed",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-77",
            },
         ],
         source: "prodsec@splunk.com",
         type: "Secondary",
      },
      {
         description: [
            {
               lang: "en",
               value: "CWE-77",
            },
         ],
         source: "nvd@nist.gov",
         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.