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

Source: https://junglewise.ai/threats/cve-2018-8024-exposure-of-sensitive-information-to-an-unauthorized-actor-in  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2019-03-14  
License: CC BY 4.0 with a link back

CVE-2018-8024 · Severity: low · CVSS 3 · Published 2019-03-14

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

Technologies: [org.apache.spark:spark-core_2.10 (Maven)](https://junglewise.ai/threats/technologies/org-apache-spark-spark-core-2-10), [org.apache.spark:spark-core_2.11 (Maven)](https://junglewise.ai/threats/technologies/org-apache-spark-spark-core-2-11). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven).

## Quick answers

**Is CVE-2018-8024 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2018-8024 being exploited in the wild.

**How severe is CVE-2018-8024?** Low severity, with a CVSS score of 3, published 14 March 2019.

**Which products and versions are affected?** org.apache.spark:spark-core_2.10 (Maven) ECOSYSTEM:introduced=2.1.0,fixed=2.1.3; org.apache.spark:spark-core_2.11 (Maven) ECOSYSTEM:introduced=2.1.0,fixed=2.1.3.

**Is there a fix for CVE-2018-8024?** Yes. org.apache.spark:spark-core_2.10 (Maven): upgrade to 2.1.3 or later; org.apache.spark:spark-core_2.11 (Maven): upgrade to 2.1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2018-8024?** Check whether you run org.apache.spark:spark-core_2.10 (Maven) or org.apache.spark:spark-core_2.11 (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.apache.spark:spark-core_2.10 (Maven): upgrade to 2.1.3 or later

  ```sh
  # set org.apache.spark:spark-core_2.10 to 2.1.3 in your pom.xml or build.gradle
  ```

- org.apache.spark:spark-core_2.11 (Maven): upgrade to 2.1.3 or later

  ```sh
  # set org.apache.spark:spark-core_2.11 to 2.1.3 in your pom.xml or build.gradle
  ```


## Affected products

- org.apache.spark:spark-core_2.10 (Maven) ECOSYSTEM:introduced=2.1.0,fixed=2.1.3
- org.apache.spark:spark-core_2.11 (Maven) ECOSYSTEM:introduced=2.1.0,fixed=2.1.3

## Identifiers

- CVE-2018-8024
- GHSA-8cw6-5qvp-q3wj

## Related threats

- [Apache Spark: Spark History Server Code Execution Vulnerability](https://junglewise.ai/threats/cve-2025-54920-apache-spark-spark-history-server-code-execution-vulnerability)
- [Apache Spark vulnerable to Log Injection](https://junglewise.ai/threats/cve-2022-31777-apache-spark-vulnerable-to-log-injection)
- [Improper Input Validation in Apache Spark](https://junglewise.ai/threats/cve-2018-11804-improper-input-validation-in-apache-spark)
- [PYSEC-2019-114 - Prior to Spark 2.3.3, in certain situations Spark would write user data to local disk unencrypted, even if spark.io.encryption.enabled=true.](https://junglewise.ai/threats/cve-2019-10099-sensitive-data-written-to-disk-unencrypted-in-spark)
- [Remote Code Execution in spark-core](https://junglewise.ai/threats/cve-2018-17190-remote-code-execution-in-spark-core)