CVE-2019-10099: 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.

CVE-2019-10099 · Severity: low · CVSS 3 · Published 2019-08-07

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. This includes cached blocks that are fetched to disk (controlled by spark.maxRemoteBlockSizeFetchToMem); in SparkR, using parallelize; in Pyspark, using broadcast and parallelize; and use of python udfs.

Technologies: org.apache.spark:spark-core_2.11 (Maven), pyspark (PyPI). Vendors: Maven, PyPI.

Quick answers

Is CVE-2019-10099 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2019-10099 being exploited in the wild.
How severe is CVE-2019-10099?
Low severity, with a CVSS score of 3, published 7 August 2019.
Which products and versions are affected?
org.apache.spark:spark-core_2.11 (Maven) ECOSYSTEM:introduced=0,fixed=2.3.3; pyspark (PyPI) ECOSYSTEM:introduced=0,fixed=2.3.3.
Is there a fix for CVE-2019-10099?
Yes. org.apache.spark:spark-core_2.11 (Maven): upgrade to 2.3.3 or later; pyspark (PyPI): upgrade to 2.3.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2019-10099?
Check whether you run 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.11 (Maven): upgrade to 2.3.3 or later
    # set org.apache.spark:spark-core_2.11 to 2.3.3 in your pom.xml or build.gradle
  • pyspark (PyPI): upgrade to 2.3.3 or later
    pip install "pyspark>=2.3.3"

Affected products

  • org.apache.spark:spark-core_2.11 (Maven) ECOSYSTEM:introduced=0,fixed=2.3.3
  • pyspark (PyPI) ECOSYSTEM:introduced=0,fixed=2.3.3

Identifiers

  • CVE-2019-10099
  • GHSA-fp5j-3fpf-mhj5
  • PYSEC-2019-114

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.