pysec-2022-236
Vulnerability from pysec
Published
2022-07-18 07:15
Modified
2022-07-25 14:38
Details

The Apache Spark UI offers the possibility to enable ACLs via the configuration option spark.acls.enable. With an authentication filter, this checks whether a user has access permissions to view or modify the application. If ACLs are enabled, a code path in HttpSecurityFilter can allow someone to perform impersonation by providing an arbitrary user name. A malicious user might then be able to reach a permission check function that will ultimately build a Unix shell command based on their input, and execute it. This will result in arbitrary shell command execution as the user Spark is currently running as. This affects Apache Spark versions 3.0.3 and earlier, versions 3.1.1 to 3.1.2, and versions 3.2.0 to 3.2.1.

Impacted products
Name purl
pyspark pkg:pypi/pyspark
Aliases


To clipboard 

{
   affected: [
      {
         package: {
            ecosystem: "PyPI",
            name: "pyspark",
            purl: "pkg:pypi/pyspark",
         },
         ranges: [
            {
               events: [
                  {
                     introduced: "0",
                  },
                  {
                     fixed: "3.1.1",
                  },
                  {
                     introduced: "3.2.0",
                  },
                  {
                     fixed: "3.2.2",
                  },
                  {
                     introduced: "3.1.1",
                  },
                  {
                     fixed: "3.1.3",
                  },
               ],
               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.2.0",
            "3.2.1",
         ],
      },
   ],
   aliases: [
      "CVE-2022-33891",
      "GHSA-4x9r-j582-cgr8",
   ],
   details: "The Apache Spark UI offers the possibility to enable ACLs via the configuration option spark.acls.enable. With an authentication filter, this checks whether a user has access permissions to view or modify the application. If ACLs are enabled, a code path in HttpSecurityFilter can allow someone to perform impersonation by providing an arbitrary user name. A malicious user might then be able to reach a permission check function that will ultimately build a Unix shell command based on their input, and execute it. This will result in arbitrary shell command execution as the user Spark is currently running as. This affects Apache Spark versions 3.0.3 and earlier, versions 3.1.1 to 3.1.2, and versions 3.2.0 to 3.2.1.",
   id: "PYSEC-2022-236",
   modified: "2022-07-25T14:38:46.692270Z",
   published: "2022-07-18T07:15:00Z",
   references: [
      {
         type: "WEB",
         url: "https://lists.apache.org/thread/p847l3kopoo5bjtmxrcwk21xp6tjxqlc",
      },
      {
         type: "ADVISORY",
         url: "https://github.com/advisories/GHSA-4x9r-j582-cgr8",
      },
   ],
}


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.