Staging Environment: Content and features may be unstable or change without notice.

Advisory Weakness Curation

CVE-2019-10099

Progress 0 / 0

Advisory Summaries

github_osv/GHSA-fp5j-3fpf-mhj5

Sensitive data written to disk unencrypted in Spark 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.

gitlab/maven/org.apache.spark/spark-core_2.11/CVE-2019-10099

Sensitive data written to disk unencrypted in Spark 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.

gitlab/maven/org.apache.spark/spark-core/CVE-2019-10099

Cryptographic Issues 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`)

gitlab/pypi/pyspark/CVE-2019-10099

Sensitive data written to disk unencrypted in Spark 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.