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

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

  # 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

  # 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