fkie_cve-2023-22942
Vulnerability from fkie_nvd
Published
2023-02-14 18:15
Modified
2024-11-21 07:45
Severity ?
5.4 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
4.3 (Medium) - CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Summary
In Splunk Enterprise versions below 8.1.13, 8.2.10, and 9.0.4, a cross-site request forgery in the Splunk Secure Gateway (SSG) app in the ‘kvstore_client’ REST endpoint lets a potential attacker update SSG KV store collections using an HTTP GET request.
References
prodsec@splunk.comhttps://advisory.splunk.com/advisories/SVD-2023-0212Vendor Advisory
prodsec@splunk.comhttps://research.splunk.com/application/4742d5f7-ce00-45ce-9c79-5e98b43b4410/Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://advisory.splunk.com/advisories/SVD-2023-0212Vendor Advisory
af854a3a-2127-422b-91ae-364da2661108https://research.splunk.com/application/4742d5f7-ce00-45ce-9c79-5e98b43b4410/Vendor Advisory
Impacted products
Vendor Product Version
splunk splunk *
splunk splunk *
splunk splunk *


To clipboard 

{
   configurations: [
      {
         nodes: [
            {
               cpeMatch: [
                  {
                     criteria: "cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*",
                     matchCriteriaId: "24C628AD-CF89-4FD5-B58F-38D150D2F535",
                     versionEndExcluding: "8.1.13",
                     versionStartIncluding: "8.1.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*",
                     matchCriteriaId: "4B2A60A4-55C6-4C11-B86D-452CC43D85FF",
                     versionEndExcluding: "8.2.10",
                     versionStartIncluding: "8.2.0",
                     vulnerable: true,
                  },
                  {
                     criteria: "cpe:2.3:a:splunk:splunk:*:*:*:*:enterprise:*:*:*",
                     matchCriteriaId: "39FFDC8F-FC45-41E7-8353-D09AAE26F50F",
                     versionEndExcluding: "9.0.4",
                     versionStartIncluding: "9.0.0",
                     vulnerable: true,
                  },
               ],
               negate: false,
               operator: "OR",
            },
         ],
      },
   ],
   cveTags: [],
   descriptions: [
      {
         lang: "en",
         value: "In Splunk Enterprise versions below 8.1.13, 8.2.10, and 9.0.4, a cross-site request forgery in the Splunk Secure Gateway (SSG) app in the ‘kvstore_client’ REST endpoint lets a potential attacker update SSG KV store collections using an HTTP GET request.",
      },
   ],
   id: "CVE-2023-22942",
   lastModified: "2024-11-21T07:45:41.390",
   metrics: {
      cvssMetricV31: [
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "LOW",
               baseScore: 5.4,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "NONE",
               integrityImpact: "LOW",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "REQUIRED",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L",
               version: "3.1",
            },
            exploitabilityScore: 2.8,
            impactScore: 2.5,
            source: "prodsec@splunk.com",
            type: "Secondary",
         },
         {
            cvssData: {
               attackComplexity: "LOW",
               attackVector: "NETWORK",
               availabilityImpact: "NONE",
               baseScore: 4.3,
               baseSeverity: "MEDIUM",
               confidentialityImpact: "NONE",
               integrityImpact: "LOW",
               privilegesRequired: "NONE",
               scope: "UNCHANGED",
               userInteraction: "REQUIRED",
               vectorString: "CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N",
               version: "3.1",
            },
            exploitabilityScore: 2.8,
            impactScore: 1.4,
            source: "nvd@nist.gov",
            type: "Primary",
         },
      ],
   },
   published: "2023-02-14T18:15:12.907",
   references: [
      {
         source: "prodsec@splunk.com",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://advisory.splunk.com/advisories/SVD-2023-0212",
      },
      {
         source: "prodsec@splunk.com",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://research.splunk.com/application/4742d5f7-ce00-45ce-9c79-5e98b43b4410/",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://advisory.splunk.com/advisories/SVD-2023-0212",
      },
      {
         source: "af854a3a-2127-422b-91ae-364da2661108",
         tags: [
            "Vendor Advisory",
         ],
         url: "https://research.splunk.com/application/4742d5f7-ce00-45ce-9c79-5e98b43b4410/",
      },
   ],
   sourceIdentifier: "prodsec@splunk.com",
   vulnStatus: "Modified",
   weaknesses: [
      {
         description: [
            {
               lang: "en",
               value: "CWE-352",
            },
         ],
         source: "prodsec@splunk.com",
         type: "Secondary",
      },
      {
         description: [
            {
               lang: "en",
               value: "CWE-352",
            },
         ],
         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.