pysec-2022-42976
Vulnerability from pysec
Published
2022-11-01 16:15
Modified
2022-11-07 01:10
Details

A stored cross-site scripting (XSS) vulnerability in Apache Spark 3.2.1 and earlier, and 3.3.0, allows remote attackers to execute arbitrary JavaScript in the web browser of a user, by including a malicious payload into the logs which would be returned in logs rendered in the UI.

Impacted products
Name purl
pyspark pkg:pypi/pyspark
Aliases



{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "pyspark",
            purl: "pkg:pypi/pyspark",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "3.2.2",
                  },
               ],
               type: "ECOSYSTEM",
            },
         ],
         versions: [
            "2.1.1",
            "2.1.2",
            "2.1.3",
            "2.2.0",
            "2.2.1",
            "2.2.2",
            "2.2.3",
            "2.3.0",
            "2.3.1",
            "2.3.2",
            "2.3.3",
            "2.3.4",
            "2.4.0",
            "2.4.1",
            "2.4.2",
            "2.4.3",
            "2.4.4",
            "2.4.5",
            "2.4.6",
            "2.4.7",
            "2.4.8",
            "3.0.0",
            "3.0.1",
            "3.0.2",
            "3.0.3",
            "3.1.1",
            "3.1.2",
            "3.1.3",
            "3.2.0",
            "3.2.1",
         ],
      },
   ],
   aliases: [
      "CVE-2022-31777",
   ],
   details: "A stored cross-site scripting (XSS) vulnerability in Apache Spark 3.2.1 and earlier, and 3.3.0, allows remote attackers to execute arbitrary JavaScript in the web browser of a user, by including a malicious payload into the logs which would be returned in logs rendered in the UI.",
   id: "PYSEC-2022-42976",
   modified: "2022-11-07T01:10:29.334199Z",
   published: "2022-11-01T16:15:00Z",
   references: [
      {
         type: "ARTICLE",
         url: "https://lists.apache.org/thread/60mgbswq2lsmrxykfxpqq13ztkm2ht6q",
      },
      {
         type: "WEB",
         url: "https://lists.apache.org/thread/60mgbswq2lsmrxykfxpqq13ztkm2ht6q",
      },
   ],
}


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.


Loading…

Loading…

Loading…

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.