Skip to content

Apache Spark UI vulnerable to Command Injection

High severity GitHub Reviewed Published May 2, 2023 to the GitHub Advisory Database • Updated Nov 12, 2023

Package

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

Affected versions

>= 3.1.1, < 3.2.2

Patched versions

3.2.2
pip pyspark (pip)
>= 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 issue was disclosed earlier as CVE-2022-33891, but incorrectly claimed version 3.1.3 (which has since gone EOL) would not be affected.

NOTE: This vulnerability only affects products that are no longer supported by the maintainer.

Users are recommended to upgrade to a supported version of Apache Spark, such as version 3.4.0.

References

Published by the National Vulnerability Database May 2, 2023
Published to the GitHub Advisory Database May 2, 2023
Reviewed May 2, 2023
Last updated Nov 12, 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

1.269%
(86th percentile)

Weaknesses

CVE ID

CVE-2023-32007

GHSA ID

GHSA-59hw-j9g6-mfg3

Source code

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