Apache SparkGHSA-fp5j-3fpf-mhj5
Sensitive data written to disk unencrypted in Spark
Fix: upgrade to 2.3.3 or later
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.
Affected versions
| Package | Affected | Fixed in |
|---|---|---|
| pyspark PyPI | < 2.3.3 | 2.3.3 |
Details and references
- CVSS 3.0
- CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Severity from
- GitHub (reviewed advisory)
- Weakness
- CWE-312
- Also known as
- CVE-2019-10099, PYSEC-2019-114
- nvd.nist.gov/vuln/detail/CVE-2019-10099
- github.com/pypa/advisory-database/tree/main/vulns/pyspark/PYSEC-2019-114.yaml
- lists.apache.org/thread.html/c2a39c207421797f82823a8aff488dcd332d9544038307bf69a2ba9e@%3Cuser.spark.apache.org%3E
- lists.apache.org/thread.html/ra216b7b0dd82a2c12c2df9d6095e689eb3f3d28164e6b6587da69fae@%3Ccommits.spark.apache.org%3E
- lists.apache.org/thread.html/rabe1d47e2bf8b8f6d9f3068c8d2679731d57fa73b3a7ed1fa82406d2@%3Cissues.spark.apache.org%3E