CVE-2019-10099 Sensitive data written to disk unencrypted in Spark
Apache Spark fails to encrypt user data written to local disk in specific scenarios, potentially exposing sensitive information to local attackers.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2019-10099?
CVE-2019-10099 is a high-severity vulnerability in Apache Spark, published on 7 Aug 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-312
Which versions are affected by CVE-2019-10099?
5 open source packages ship an affected version, including org.apache.spark:spark-core_2.11 and pyspark. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
org.apache.spark:spark-core_2.11 Maven | All versions | 2.3.3 |
org.apache.spark:spark-core_2.11 Maven | All versions | 2.3.3 |
pyspark PyPI | All versions | 2.3.3 |
pyspark PyPI | All versions | 2.3.3 |
pyspark PyPI | All versions | 2.3.3 |
Products include Apache Spark.
How do I fix CVE-2019-10099?
Upgrade org.apache.spark:spark-core_2.11 to 2.3.3 or later.
Is CVE-2019-10099 being exploited?
There is no known exploitation of CVE-2019-10099 in the wild and no public exploit code.
Other vulnerabilities in Apache Spark
Sources
Also known as GHSA-fp5j-3fpf-mhj5, PYSEC-2019-114.