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.
References
Link | Resource |
---|---|
https://lists.apache.org/thread.html/c2a39c207421797f82823a8aff488dcd332d9544038307bf69a2ba9e@%3Cuser.spark.apache.org%3E | Mailing List Vendor Advisory |
https://lists.apache.org/thread.html/rabe1d47e2bf8b8f6d9f3068c8d2679731d57fa73b3a7ed1fa82406d2@%3Cissues.spark.apache.org%3E | Mailing List Vendor Advisory |
https://lists.apache.org/thread.html/ra216b7b0dd82a2c12c2df9d6095e689eb3f3d28164e6b6587da69fae@%3Ccommits.spark.apache.org%3E | Mailing List Patch Vendor Advisory |
Configurations
Configuration 1 (hide)
|
Information
Published : 2019-08-07 10:15
Updated : 2022-04-22 13:11
NVD link : CVE-2019-10099
Mitre link : CVE-2019-10099
JSON object : View
CWE
CWE-312
Cleartext Storage of Sensitive Information
Products Affected
apache
- spark