CVE-2019-10099

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.

Published: 2019-08-07 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2019-10099 is rated Moderate Risk (47.9/100): CVSS High severity, with medium exploitation likelihood (EPSS 0.29%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2019-10099

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-03 0.54% 0.29% -0.26%
2 2025-12-10 0.58% 0.54% -0.04%
3 2025-11-21 — 0.58% —

Full EPSS history (15 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2019-10099

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.5 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 3.6 [email protected]
4.3 2.0 MEDIUM
AV:N/AC:M/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:M)
Exploitation needs some favorable conditions, but not exceptional ones.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
 8.6 2.9 [email protected]

Weakness enumeration for CVE-2019-10099

GitHub Security Advisory for CVE-2019-10099

GHSA-fp5j-3fpf-mhj5 · Severity: high · Ecosystem: maven — Sensitive data written to disk unencrypted in Spark

OS Trackers for CVE-2019-10099

vendor priority summary link
suse medium CVE-2019-10099 severity moderate: SUSE including 1 source package names (spark), 5 product×package rows across 5 product lines (HPE Helion OpenStack 8, SUSE OpenStack Cloud 8, … (5 product lines)): Known Not Affected 5. https://www.suse.com/security/cve/CVE-2019-10099/

Affected software / configurations for CVE-2019-10099

Vendor Product Version Raw CPE
apache spark >= 1.0.2, <= 1.6.3 cpe:2.3:a:apache:spark:*:*:*:*:*:*:*:*
apache spark >= 2.0.0, <= 2.0.2 cpe:2.3:a:apache:spark:*:*:*:*:*:*:*:*
apache spark >= 2.1.0, <= 2.1.3 cpe:2.3:a:apache:spark:*:*:*:*:*:*:*:*
apache spark >= 2.2.0, <= 2.2.2 cpe:2.3:a:apache:spark:*:*:*:*:*:*:*:*
apache spark >= 2.3.0, < 2.3.2 cpe:2.3:a:apache:spark:*:*:*:*:*:*:*:*

References for CVE-2019-10099

cvelogic Threat Intelligence