Skip to content

Apache Spark vulnerable to Improper Privilege Management

Critical severity GitHub Reviewed Published Apr 17, 2023 to the GitHub Advisory Database • Updated Oct 15, 2024

Package

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

Affected versions

<= 3.3.2

Patched versions

3.3.3
maven org.apache.spark:spark-core_2.13 (Maven)
<= 3.3.2
3.3.3
pip pyspark (pip)
< 3.3.2
3.3.2

Description

In Apache Spark versions prior to versions 3.4.0 and 3.3.3, applications using spark-submit can specify a proxy-user to run as, limiting privileges. The application can execute code with the privileges of the submitting user, however, by providing malicious configuration-related classes on the classpath. This affects architectures relying on proxy-user, for example those using Apache Livy to manage submitted applications.

Update to Apache Spark 3.4.0, 3.3.3, or later, and ensure that spark.submit.proxyUser.allowCustomClasspathInClusterMode is set to its default of "false", and is not overridden by submitted applications.

References

Published by the National Vulnerability Database Apr 17, 2023
Published to the GitHub Advisory Database Apr 17, 2023
Reviewed Apr 21, 2023
Last updated Oct 15, 2024

Severity

Critical

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
Changed
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:C/C:H/I:H/A:H

EPSS score

0.137%
(50th percentile)

Weaknesses

CVE ID

CVE-2023-22946

GHSA ID

GHSA-329j-jfvr-rhr6

Source code

Credits

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