DescriptionPrior 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.
Overall state of this security issue: Resolved
This issue is currently rated as having moderate severity.
|National Vulnerability Database|
|National Vulnerability Database||SUSE|
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification. The updates are grouped by state of their lifecycle. SUSE product lifecycles are documented on the lifecycle page.
|Products past their end of life and not receiving proactive updates anymore.|
|HPE Helion OpenStack 8||spark||Not affected|
|SUSE Manager Server 3.1||spark||Unsupported|
|SUSE OpenStack Cloud 8||spark||Not affected|
|SUSE OpenStack Cloud 9||spark||Not affected|
|SUSE OpenStack Cloud Crowbar 8||spark||Not affected|
|SUSE OpenStack Cloud Crowbar 9||spark||Not affected|
SUSE Timeline for this CVECVE page created: Wed Aug 7 21:57:44 2019
CVE page last modified: Mon Sep 11 19:57:26 2023