CVE-2018-1334: Exposure of Sensitive Information to an Unauthorized Actor in Apache Spark
CVE-2018-1334 · Severity: low · CVSS 3 · Published 2018-07-12
In Apache Spark 1.0.0 to 2.1.2, 2.2.0 to 2.2.1, and 2.3.0, when using PySpark or SparkR, it's possible for a different local user to connect to the Spark application and impersonate the user running the Spark application.
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; pyspark (PyPI): upgrade to 2.1.3, 2.2.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2018-1334?
Check whether you run org.apache.spark:spark-core_2.10 (Maven), org.apache.spark:spark-core_2.11 (Maven) or pyspark (PyPI) 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