Moderate severity vulnerability that affects org.apache.spark:spark-core_2.10 and org.apache.spark:spark-core_2.11
In Apache Spark before 2.2.0, it is possible for an attacker to take advantage of a user's trust in the server to trick them into visiting a link that points to a shared Spark cluster and submits data including MHTML to the Spark master, or history server. This data, which could contain a script, would then be reflected back to the user and could be evaluated and executed by MS Windows-based clients. It is not an attack on Spark itself, but on the user, who may then execute the script inadvertently when viewing elements of the Spark web UIs.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Java / Kotlin (Maven) | org.apache.spark:spark-core_2.10 | < 2.2.0 | 2.2.0 |
| Java / Kotlin (Maven) | org.apache.spark:spark-core_2.11 | < 2.2.0 | 2.2.0 |
References
- CVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N- Weakness (CWE)
CWE-79- Platform
- Java / Kotlin (Maven)
- Package
org.apache.spark:spark-core_2.10, org.apache.spark:spark-core_2.11- Disclosed
- 09.11.2018
- Updated
- 11.10.2026 11:20
Sources and licenses
OSV / GitHub Advisory Database - GHSA-r34r-f84j-5x4x - CC BY 4.0
Vulnerability history: org.apache.spark:spark-core_2.10
All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 9
- First → latest
- 09.2017 03.2026
- Without a fix
- 5
- Exploited in attacks
- 0
Severity breakdown
- Critical 1
- High 3
- Medium 5
Disclosures per year
- 2017: 1
- 2018: 4
- 2019: 1
- 2020: 0
- 2021: 0
- 2022: 2
- 2023: 0
- 2024: 0
- 2025: 0
- 2026: 1
-
Moderate severity vulnerability that affects org.apache.spark:spark-core_2.10 and org.apache.spark:spark-core_2.11 this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.