Skip to content

Apache Spark vulnerable to Improper Privilege Management

Critical severity GitHub Reviewed Published Apr 17, 2023 to the GitHub Advisory Database • Updated Aug 21, 2023

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

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 Aug 21, 2023

Severity

Critical
10.0
/ 10

CVSS base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Weaknesses

CVE ID

CVE-2023-22946

GHSA ID

GHSA-329j-jfvr-rhr6

Source code

Credits

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