Description
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.
Analysis and contextual insights are available on OpenCVE Cloud.
Remediation
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2019-0110 | 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. |
Github GHSA |
GHSA-fp5j-3fpf-mhj5 | Sensitive data written to disk unencrypted in Spark |
References
History
No history.
Status: PUBLISHED
Assigner: apache
Published:
Updated: 2024-08-04T22:10:09.549Z
Reserved: 2019-03-26T00:00:00.000Z
Link: CVE-2019-10099
No data.
Status : Modified
Published: 2019-08-07T17:15:12.073
Modified: 2024-11-21T04:18:24.237
Link: CVE-2019-10099
No data.
OpenCVE Enrichment
No data.
Weaknesses
EUVD
Github GHSA