Exposure of Sensitive Information to an Unauthorized Actor in Apache Spark via crafted URL (CVE-2018-8024)

Exposure of Sensitive Information to an Unauthorized Actor in Apache Spark via crafted URL (CVE-2018-8024) | HOL Guard CVE

Why this deserves its current priority

CVSS is 5.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps org.apache.spark:spark-core_2.10 (maven), org.apache.spark:spark-core_2.10 (maven), org.apache.spark:spark-core_2.11 (maven), org.apache.spark:spark-core_2.11 (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
org.apache.spark:spark-core_2.10maven	>=2.1.0 <2.1.3	2.1.3
org.apache.spark:spark-core_2.10maven	>=2.2.0 <2.2.2	2.2.2
org.apache.spark:spark-core_2.11maven	>=2.1.0 <2.1.3	2.1.3
org.apache.spark:spark-core_2.11maven	>=2.2.0 <2.2.2	2.2.2
org.apache.spark:spark-core_2.11maven	>=2.3.0 <2.3.1	2.3.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for org.apache.spark:spark-core_2.10, org.apache.spark:spark-core_2.10, org.apache.spark:spark-core_2.11.
Review the reported fix. Update org.apache.spark:spark-core_2.10 to 2.1.3; org.apache.spark:spark-core_2.10 to 2.2.2; org.apache.spark:spark-core_2.11 to 2.1.3; org.apache.spark:spark-core_2.11 to 2.2.2; org.apache.spark:spark-core_2.11 to 2.3.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Mar 14, 2019
Evidence: source:osv:source_dates:source-dates:record
Source modified
Sep 10, 2026
Evidence: source:osv:source_dates:source-dates:record
First seen by HOL
Sep 10, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.