pysec-2023-44
Vulnerability from pysec
Published
2023-04-17 08:15
Modified
2023-05-04 03:49
Details
In Apache Spark versions prior to 3.4.0, 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 or later, and ensure that spark.submit.proxyUser.allowCustomClasspathInClusterMode is set to its default of "false", and is not overridden by submitted applications.
Impacted products
Name | purl |
---|---|
pyspark | pkg:pypi/pyspark |
Aliases
{ affected: [ { package: { ecosystem: "PyPI", name: "pyspark", purl: "pkg:pypi/pyspark", }, ranges: [ { events: [ { introduced: "0", }, { fixed: "3.4.0", }, ], 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.1.3", "3.2.0", "3.2.1", "3.2.2", "3.2.3", "3.2.4", "3.3.0", "3.3.1", "3.3.2", ], }, ], aliases: [ "CVE-2023-22946", ], details: "In Apache Spark versions prior to 3.4.0, 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.\n\nUpdate to Apache Spark 3.4.0 or later, and ensure that \nspark.submit.proxyUser.allowCustomClasspathInClusterMode is set to its \ndefault of \"false\", and is not overridden by submitted applications.\n\n\n", id: "PYSEC-2023-44", modified: "2023-05-04T03:49:47.415944Z", published: "2023-04-17T08:15:00Z", references: [ { type: "ARTICLE", url: "https://lists.apache.org/thread/yllfl25xh5tbotjmg93zrq4bzwhqc0gv", }, { type: "ADVISORY", url: "https://lists.apache.org/thread/yllfl25xh5tbotjmg93zrq4bzwhqc0gv", }, ], }
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.
Title of the comment
Description of the comment
Loading…
Loading…
Loading…
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.