CVE-2019-10099
First published: Wed Aug 07 2019(Updated: )
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.
Credit: security@apache.org security@apache.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Apache Spark | >=1.0.2<=1.6.3 | |
| Apache Spark | >=2.0.0<=2.0.2 | |
| Apache Spark | >=2.1.0<=2.1.3 | |
| Apache Spark | >=2.2.0<=2.2.2 | |
| Apache Spark | >=2.3.0<2.3.2 | |
| pip/pyspark | >=0<2.3.3 | 2.3.3 |
| maven/org.apache.spark:spark-core_2.11 | <2.3.3 | 2.3.3 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- https://lists.apache.org/thread.html/c2a39c207421797f82823a8aff488dcd332d9544038307bf69a2ba9e@%3Cuser.spark.apache.org%3E
- https://lists.apache.org/thread.html/ra216b7b0dd82a2c12c2df9d6095e689eb3f3d28164e6b6587da69fae@%3Ccommits.spark.apache.org%3E
- https://lists.apache.org/thread.html/rabe1d47e2bf8b8f6d9f3068c8d2679731d57fa73b3a7ed1fa82406d2@%3Cissues.spark.apache.org%3E
- https://lists.apache.org/thread.html/c2a39c207421797f82823a8aff488dcd332d9544038307bf69a2ba9e%40%3Cuser.spark.apache.org%3E
- https://lists.apache.org/thread.html/rabe1d47e2bf8b8f6d9f3068c8d2679731d57fa73b3a7ed1fa82406d2%40%3Cissues.spark.apache.org%3E
- https://lists.apache.org/thread.html/ra216b7b0dd82a2c12c2df9d6095e689eb3f3d28164e6b6587da69fae%40%3Ccommits.spark.apache.org%3E
- https://nvd.nist.gov/vuln/detail/CVE-2019-10099
- https://github.com/pypa/advisory-database/tree/main/vulns/pyspark/PYSEC-2019-114.yaml
- https://github.com/advisories/GHSA-fp5j-3fpf-mhj5 (Advisory)
Frequently Asked Questions
What is the severity of CVE-2019-10099?
The severity of CVE-2019-10099 is rated as high with a score of 7.5.
How can I mitigate the impact of CVE-2019-10099?
To mitigate CVE-2019-10099, users should upgrade to Spark version 2.3.3 or higher where the vulnerability has been fixed.
Which versions of Apache Spark are affected by CVE-2019-10099?
CVE-2019-10099 affects Apache Spark versions ranging from 1.0.2 to 2.3.2.
What type of vulnerability is CVE-2019-10099?
CVE-2019-10099 is classified under CWE-312, which is related to cleartext storage of sensitive information vulnerability.
- collector/nvd-index
- agent/type
- collector/mitre-cve
- source/MITRE
- agent/remedy
- agent/weakness
- agent/description
- agent/first-publish-date
- collector/github-advisory-latest
- source/GitHub
- alias/GHSA-fp5j-3fpf-mhj5
- alias/CVE-2019-10099
- agent/software-canonical-lookup
- agent/last-modified-date
- agent/softwarecombine
- agent/severity
- agent/references
- agent/event
- collector/nvd-cve
- source/NVD
- agent/author
- collector/github-advisory
- agent/tags
- agent/trending
- vendor/apache
- canonical/apache spark
- version/apache spark/1.0.2
- version/apache spark/1.6.3
- version/apache spark/2.0.0
- version/apache spark/2.0.2
- version/apache spark/2.1.0
- version/apache spark/2.1.3
- version/apache spark/2.2.0
- version/apache spark/2.2.2
- version/apache spark/2.3.0
- package-manager/pip
- package-manager/maven