# CVE-2018-8024: Exposure of Sensitive Information to an Unauthorized Actor in Apache Spark via crafted URL > A malicious user can trick victims into visiting a crafted URL to execute scripts and expose Spark UI information, primarily affecting Firefox users. - **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 12 Jul 2018 - **Updated:** 17 Sep 2024 - **Also known as:** GHSA-8cw6-5qvp-q3wj ## What is CVE-2018-8024? CVE-2018-8024 is a medium-severity cross-site scripting vulnerability in Mozilla Firefox, published on 12 Jul 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. ### Official description In Apache Spark 2.1.0 to 2.1.2, 2.2.0 to 2.2.1, and 2.3.0, it's possible for a malicious user to construct a URL pointing to a Spark cluster's UI's job and stage info pages, and if a user can be tricked into accessing the URL, can be used to cause script to execute and expose information from the user's view of the Spark UI. While some browsers like recent versions of Chrome and Safari are able to block this type of attack, current versions of Firefox (and possibly others) do not. Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) ## Which versions are affected by CVE-2018-8024? 10 open source packages ship an affected version, including org.apache.spark:spark-core_2.11 and org.apache.spark:spark-core_2.10. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.spark:spark-core_2.11` | Maven | From 2.1.0 | 2.1.3 | | `org.apache.spark:spark-core_2.11` | Maven | From 2.1.0 | 2.1.3 | | `org.apache.spark:spark-core_2.11` | Maven | From 2.2.0 | 2.2.2 | | `org.apache.spark:spark-core_2.11` | Maven | From 2.2.0 | 2.2.2 | | `org.apache.spark:spark-core_2.11` | Maven | From 2.3.0 | 2.3.1 | | `org.apache.spark:spark-core_2.11` | Maven | From 2.3.0 | 2.3.1 | | `org.apache.spark:spark-core_2.10` | Maven | From 2.1.0 | 2.1.3 | | `org.apache.spark:spark-core_2.10` | Maven | From 2.1.0 | 2.1.3 | | `org.apache.spark:spark-core_2.10` | Maven | From 2.2.0 | 2.2.2 | | `org.apache.spark:spark-core_2.10` | Maven | From 2.2.0 | 2.2.2 | Products: Apache Spark, Mozilla Firefox. ## How do I fix CVE-2018-8024? Upgrade org.apache.spark:spark-core_2.11 to a fixed version for your release line: 2.1.3, 2.2.2 or 2.3.1. ## Is CVE-2018-8024 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-8024 exists. Public exploit code: - Apache Spark UI - Cross-Site Scripting (nuclei): http/cves/2018/CVE-2018-8024.yaml ## Other vulnerabilities in Mozilla Firefox - [CVE-2022-33891](https://insights.sbomify.com/CVE-2022-33891/): Apache Spark Command Injection (high 8.8, exploited in the wild) - [CVE-2020-9480](https://insights.sbomify.com/CVE-2020-9480/): Improper Authentication in Apache Spark (critical 9.8) - [CVE-2018-17190](https://insights.sbomify.com/CVE-2018-17190/): Remote Code Execution in spark-core (critical 9.8) - [CVE-2019-20445](https://insights.sbomify.com/CVE-2019-20445/): HTTP Request Smuggling in Netty (critical 9.1) - [CVE-2025-54920](https://insights.sbomify.com/CVE-2025-54920/): Apache Spark: Spark History Server Code Execution Vulnerability (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2018-8024 and fix it if it is affected. What it is: CVE-2018-8024 is a medium-severity cross-site scripting vulnerability in Mozilla Firefox, published on 12 Jul 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2018-8024 exists. Affected packages and fixed versions: - org.apache.spark:spark-core_2.11 (Maven): affected from 2.1.0; fixed in 2.1.3 - org.apache.spark:spark-core_2.11 (Maven): affected from 2.1.0; fixed in 2.1.3 - org.apache.spark:spark-core_2.11 (Maven): affected from 2.2.0; fixed in 2.2.2 - org.apache.spark:spark-core_2.11 (Maven): affected from 2.2.0; fixed in 2.2.2 - org.apache.spark:spark-core_2.11 (Maven): affected from 2.3.0; fixed in 2.3.1 - org.apache.spark:spark-core_2.11 (Maven): affected from 2.3.0; fixed in 2.3.1 - org.apache.spark:spark-core_2.10 (Maven): affected from 2.1.0; fixed in 2.1.3 - org.apache.spark:spark-core_2.10 (Maven): affected from 2.1.0; fixed in 2.1.3 - org.apache.spark:spark-core_2.10 (Maven): affected from 2.2.0; fixed in 2.2.2 - org.apache.spark:spark-core_2.10 (Maven): affected from 2.2.0; fixed in 2.2.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2018-8024/ (Markdown: https://insights.sbomify.com/CVE-2018-8024/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2018-8024 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-8024 - OSV: https://osv.dev/vulnerability/CVE-2018-8024 --- From sbomify Insights: https://insights.sbomify.com/CVE-2018-8024/ Summaries are generated and may contain mistakes; the official description above is the record.