SparkApplication · Apache
CVE-2018-8024
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceApache Spark versions 2.1.0-2.1.2, 2.2.0-2.2.1, and 2.3.0 contain a cross-site scripting (XSS) vulnerability in the Spark UI's job and stage information pages. Attackers can craft malicious URLs that, when accessed by victims, execute arbitrary JavaScript in the context of the Spark UI, potentially exposing sensitive information from the user's session.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
SparkApplication
>= 2.1.0, <= 2.1.2>= 2.2.0, <= 2.2.1= 2.3.0
FirefoxWeb browser
all versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Apache Spark versionRun `spark-submit --version` or inspect the Spark UI footer for the version number. If you have access to the Spark home directory, check the RELEASE file or jar file names.Affected if The installed version is 2.1.0, 2.1.1, 2.1.2, 2.2.0, 2.2.1, or 2.3.0.
-
Verify Spark UI is enabledCheck the Spark configuration for `spark.ui.enabled` (default true) or look for the UI process running on the configured port (default 4040 for live applications, 8080 for standalone cluster).Affected if The Spark UI is enabled and accessible.
-
Check UI network bindingInspect `spark.ui.bindAddress` and `spark.master.rest.enabled` configuration settings. Look at how the Spark UI service is bound (0.0.0.0 vs 127.0.0.1).Affected if The Spark UI is bound to all network interfaces (0.0.0.0) or otherwise accessible from untrusted network segments.
-
Check UI authenticationReview whether `spark.ui.acls.enable` or `spark.ui.authorization.enabled` is configured, and if Spark authentication (spark.authenticate) is enabled.Affected if No authentication or authorization controls are enabled for the Spark UI.
You are affected if your Spark version is 2.1.0-2.1.2, 2.2.0-2.2.1, or 2.3.0 AND the Spark UI is enabled and accessible to users who could craft malicious URLs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade to Apache Spark 2.1.3, 2.2.2, 2.3.1, or later. If immediate patching is not feasible, consider restricting access to the Spark UI via network controls or authentication.
Fix this in Spark
Scoped from the published advisory
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-8024 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-8024 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data