How severe is CVE-2018-8024?

CVE-2018-8024 has a CVSS score of 5.4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2018-8024?

CVE-2018-8024 affects the following packages: 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), org.apache.spark:spark-core_2.11 (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-8024?

Update org.apache.spark:spark-core_2.10 to 2.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-8024 is resolved across your whole dependency graph.

How do I detect CVE-2018-8024 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.spark:spark-core_2.10, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2018-8024 if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is CVE-2018-8024 actively exploited in the wild?

No public exploit code has been indexed for CVE-2018-8024 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2018-8024?

CVE-2018-8024 has an EPSS (Exploit Prediction Scoring System) score of 5.3%, placing it in the 93th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2018-8024?

CVE-2018-8024 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

Is there exploit tooling available for CVE-2018-8024?

A Nuclei detection template exists for CVE-2018-8024, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2018-8024 published, and has it been updated?

CVE-2018-8024 was published on July 12, 2018 and was last updated on October 24, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

MEDIUM severity

CVE-2018-8024 — spark-core_2.10

MEDIUM

CVE-2018-8024 is a medium-severity (CVSS 5.4) Information Exposure vulnerability in org.apache.spark:spark-core_2.10. A fix is available for org.apache.spark:spark-core_2.10 — see the affected versions and patch details below.

Exposure of Sensitive Information to an Unauthorized Actor in Apache Spark via crafted URL

Also known asGHSA-8cw6-5qvp-q3wj

Published

Jul 12, 2018

Updated

Oct 24, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

5.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs93th percentile — riskier than 93% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected

☕org.apache.spark:spark-core_2.10☕org.apache.spark:spark-core_2.10☕org.apache.spark:spark-core_2.11☕org.apache.spark:spark-core_2.11☕org.apache.spark:spark-core_2.11

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

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.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.apache.spark:spark-core_2.10`	≥ 2.1.0&&< 2.1.3	2.1.3`org.apache.spark:spark-core_2.10:2.1.3`
☕Maven	`org.apache.spark:spark-core_2.10`	≥ 2.2.0&&< 2.2.2	2.2.2`org.apache.spark:spark-core_2.10:2.2.2`
☕Maven	`org.apache.spark:spark-core_2.11`	≥ 2.1.0&&< 2.1.3	2.1.3`org.apache.spark:spark-core_2.11:2.1.3`
☕Maven	`org.apache.spark:spark-core_2.11`	≥ 2.2.0&&< 2.2.2	2.2.2`org.apache.spark:spark-core_2.11:2.2.2`
☕Maven	`org.apache.spark:spark-core_2.11`	≥ 2.3.0&&< 2.3.1	2.3.1`org.apache.spark:spark-core_2.11:2.3.1`

Affected Products

2 products · 4 configurations

Application

sparkapache

≥ 2.2.0 && ≤ 2.2.1

1 version

2.3.0

Application

firefoxmozilla

all

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.spark:spark-core_2.10, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.spark:spark-core_2.10 to 2.1.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2018-8024 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

How to detect CVE-2018-8024

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2018-8024 -u https://target

Template: Apache Spark UI - Cross-Site Scripting
Severity: medium
Impact: Attackers can execute arbitrary JavaScript in victims' browsers via crafted query string parameters, potentially stealing session cookies or performing actions on behalf of users.
Remediation: Upgrade to Apache Spark version 2.3.2 or later.

Template by ProjectDiscovery nuclei-templates (ritikchaddha), MIT licensed. View the full template. Scan only systems you are authorised to test.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2018-8024 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

5.4/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Raw vector

CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

CWE Classification

CWE-200Information Exposure

Weaponization

Timeline

Disclosed

Jul 12, 2018

Last updated

Oct 24, 2026

Identifiers

CVE-2018-8024

GHSA-8cw6-5qvp-q3wj

References

Advisoryspark.apache.org · security Advisorynvd.nist.gov · CVE 2018 8024 Advisorygithub.com · GHSA 8cw6 5qvp q3wj Weblists.apache.org · 5f241d2cda21cbcb3b63e46e474cf5f50cce66927f08399f4fab0aba@<dev.spark.apache.org>Weblists.apache.org · 5f241d2cda21cbcb3b63e46e474cf5f50cce66927f08399f4fab0aba@<dev.spark.apache.org>

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting spark-core_2.10 are rated as high or higher (top: critical).

CVE-2025-54920CVE-2022-31777CVE-2018-11804CVE-2018-1334CVE-2018-17190CVE-2017-12612CVE-2017-7678CVE-2018-11770

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 24, 2026