CVE-2019-10099 json
Sensitive data written to disk unencrypted in Spark
published 7y ago modified 4mo ago also GHSA-fp5j-3fpf-mhj5 , PYSEC-2019-114 , EUVD-2019-0110
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- maven org.apache.spark:spark-core_2.11 2.3.3
- pypi pyspark 2.3.3
- apache spark 2.3.2
Is CVE-2019-10099 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.31% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:P/I:N/A:N |
| GitHub | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.apache.spark:spark-core_2.11 | <2.3.3 |
2.3.3 |
| pypi | pyspark | <2.3.3 |
2.3.3 |
Affected products
- Apache Apache Spark
Classification
- Weakness
-
- CWE-312 Cleartext Storage of Sensitive Information
References
- lists.apache.org /thread.html/c2a39c207421797f82823a8aff488dcd332d9544038307bf69a2ba9e%40%3Cuser.spark.apache.org%3E
-
lists.apache.org
/thread.html/rabe1d47e2bf8b8f6d9f3068c8d2679731d57fa73b3a7ed1fa82406d2%40%3Cissues.spark.apache.org%3E
mailing-list
-
lists.apache.org
/thread.html/ra216b7b0dd82a2c12c2df9d6095e689eb3f3d28164e6b6587da69fae%40%3Ccommits.spark.apache.org%3E
mailing-list
-
nvd.nist.gov
/vuln/detail/CVE-2019-10099
advisory
-
github.com
/pypa/advisory-database/tree/main/vulns/pyspark/PYSEC-2019-114.yaml
web
-
lists.apache.org
/thread.html/c2a39c207421797f82823a8aff488dcd332d9544038307bf69a2ba9e@%3Cuser.spark.apache.org%3E
web
-
lists.apache.org
/thread.html/ra216b7b0dd82a2c12c2df9d6095e689eb3f3d28164e6b6587da69fae@%3Ccommits.spark.apache.org%3E
web
-
lists.apache.org
/thread.html/rabe1d47e2bf8b8f6d9f3068c8d2679731d57fa73b3a7ed1fa82406d2@%3Cissues.spark.apache.org%3E
web
-
github.com
/advisories/GHSA-fp5j-3fpf-mhj5
advisory
Sources
- CVE List CVE-2019-10099
- GitHub Advisory GHSA-fp5j-3fpf-mhj5
- NVD CVE-2019-10099
- OSV PYSEC-2019-114
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.