CVE-2019-10099

7.5 HIGH 1% exploit odds No fix listed

What it is

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.

At a glance

Exploitability: Can be exploited over the network without logging in. High risk of data exposure.
Exploit odds: 1.3% chance of exploitation in the next 30 days (EPSS).
Fix: No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

2019-08-07 17:15 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-06-17 02:10 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 1.3% in the next 30 days (EPSS).
Severity: 7.5 HIGH (CVSS).
Fix: none linked yet, which raises it.

Details

Published: 2019-08-07 17:15 UTC
Last modified: 2026-06-17 02:10 UTC
Exploit probability: 1.3% · EPSS, next 30 days
Weakness: CWE-312
Record status: Modified

Affected

Apache Spark ≤ 1.6.3
Apache Spark ≤ 2.0.2
Apache Spark ≤ 2.1.3
Apache Spark ≤ 2.2.2
Apache Spark < 2.3.2

Attack profile CVSS 3.1 · 7.5

Attack vector: Network
Complexity: Low
Privileges needed: None
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2019-10099.md and follow it. Check whether this project is affected by CVE-2019-10099. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

References

NVD record · CVE.org record