# 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.

Source: https://junglewise.ai/threats/cve-2019-10099-sensitive-data-written-to-disk-unencrypted-in-spark  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2019-08-07  
License: CC BY 4.0 with a link back

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)](https://junglewise.ai/threats/technologies/org-apache-spark-spark-core-2-11), [pyspark (PyPI)](https://junglewise.ai/threats/technologies/pyspark). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven), [PyPI](https://junglewise.ai/threats/vendors/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

  ```sh
  # 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

  ```sh
  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

## Related threats

- [Apache Spark History Server XSS in job names](https://junglewise.ai/threats/cve-2026-32773-apache-spark-history-server-xss-in-job-names)
- [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 Inadequate Encryption Strength in RPC Communication](https://junglewise.ai/threats/cve-2025-55039-apache-spark-inadequate-encryption-strength-in-rpc-communication)
- [Apache Spark UI vulnerable to Command Injection](https://junglewise.ai/threats/cve-2023-32007-apache-spark-ui-vulnerable-to-command-injection)
- [Apache Spark privilege escalation via classpath injection](https://junglewise.ai/threats/cve-2023-22946-apache-spark-privilege-escalation-via-classpath-injection)