Skip to content

Apache Spark UI can allow impersonation if ACLs enabled

High severity GitHub Reviewed Published Jul 19, 2022 to the GitHub Advisory Database • Updated Aug 31, 2023

Package

maven org.apache.spark:spark-parent_2.12 (Maven)

Affected versions

<= 3.0.3
>= 3.1.1, < 3.2.2

Patched versions

3.2.2
pip pyspark (pip)
>= 0, <= 3.0.3
>= 3.1.1, < 3.2.2
3.2.2

Description

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.

A previous version of this advisory incorrectly stated that version 3.1.3 was not vulnerable. Per GHSA-59hw-j9g6-mfg3, version 3.1.3 is vulnerable and vulnerable version ranges in this advisory have been changed to reflect the correct information.

References

Published by the National Vulnerability Database Jul 18, 2022
Published to the GitHub Advisory Database Jul 19, 2022
Reviewed Jul 21, 2022
Last updated Aug 31, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

EPSS score

97.310%
(100th percentile)

Weaknesses

CVE ID

CVE-2022-33891

GHSA ID

GHSA-4x9r-j582-cgr8

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.