Apache Spark: XSS Vulnerability in Spark Web 3.5.4
Apache Software Foundation Apache Spark
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| pyspark PyPI |
|
|
| org.apache.spark:spark-core_2.12 Maven |
|
|
| org.apache.spark:spark-core_2.13 Maven |
Apache Software Foundation Apache Spark
| Product | Affected | Fixed in |
|---|---|---|
| pyspark PyPI |
|
|
| org.apache.spark:spark-core_2.12 Maven |
|
|
| org.apache.spark:spark-core_2.13 Maven |
|
|
There is a lack of XSS escaping in the Spark History Server prior to 3.5.8 which allows a malicious Spark job to generate arbitrary unescaped frontend code which could lead to a minimal privilege escalation in browser. Users are encouraged to upgrade to Spark 3.5.8 or later.
This CVE is marked as "low" since the path to exploit requires both relatively high permissions (ability to launch a Spark job) and requires tricking a user with higher permissions to log in and visit the Spark history web page.
Users are encouraged to upgrade their Spark history servers to Spark 3.5.8 or later.
From the CVE record · apache
The Spark History Server before 3.5.8 does not escape some frontend content, allowing a malicious Spark job to generate arbitrary unescaped code. Exploitation requires permission to launch a Spark job and tricking a higher-privileged user into logging in and visiting the Spark history web page; this could lead to limited privilege escalation in their browser.
Operators of Spark History Server and users of PyPI pyspark or Maven org.apache.spark:spark-core_2.12 or spark-core_2.13 versions 3.0.0 through versions before 3.5.8 should check.