CVE-2019-10099

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.

Risk Information

Base Score
7.5
MODERATE
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS Score
Exploitation Probability
0.542

Associated Vulnerability

VulnerabilityOS Platform
Vulnerabilities CVE-2019-10099 are fixed in Apache-spark-core_2.11 2.3.3Windows
Vulnerabilities CVE-2019-10099 are fixed in Python-pyspark 2.3.3Windows
Vulnerabilities CVE-2019-10099 are fixed in Apache-spark-core_2.11 for Linux 2.3.3Linux
Vulnerabilities CVE-2019-10099 are fixed in Python-pyspark for linux 2.3.3Linux

Patch Details

No records found

References

https://nvd.nist.gov/vuln/detail/CVE-2023-1234
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1234