Apache Spark Deserialization of Untrusted Data vulnerability

published 2017-09-13 9y ago modified 2026-06-17 4mo ago also GHSA-8rhc-48pp-52gr , PYSEC-2017-147 , EUVD-2017-0107

cvss: 7.8; version 3.0, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.7%; EPSS 0.7% chance of exploitation in 30 days, percentile 54%
public exploits: 0; none known

In Apache Spark 1.6.0 until 2.1.1, the launcher API performs unsafe deserialization of data received by its socket. This makes applications launched programmatically using the launcher API potentially vulnerable to arbitrary code execution by an attacker with access to any user account on the local machine. It does not affect apps run by spark-submit or spark-shell. The attacker would be able to execute code as the user that ran the Spark application. Users are encouraged to update to version 2.2.0 or later.

Patch / fix

fixed in 3

maven org.apache.spark:spark-core_2.11 2.1.2
maven org.apache.spark:spark-core_2.10 2.1.2
pypi pyspark 2.1.2

Is CVE-2017-12612 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

0.73% chance of exploitation in the next 30 days, higher than 54% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.0	7.8	CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD	2.0	7.2	AV:L/AC:L/Au:N/C:C/I:C/A:C
GitHub	3.0	7.8	CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OSV	3.0	7.8	CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem	package	affected	fixed in
maven	org.apache.spark:spark-core_2.11	<2.1.2	2.1.2
maven	org.apache.spark:spark-core_2.10	<2.1.2	2.1.2
pypi	pyspark	<2.1.2	2.1.2

Classification

Weakness

CWE-502 Deserialization of Untrusted Data

References

mail-archives.apache.org /mod_mbox/spark-dev/201709.mbox/%3CCAEccTyy-1yYuhdNgkBUg0sr9NeaZSrBKkBePdTNZbxXZNTAR-g%40mail.gmail.com%3E
web, mailing-list, vendor-advisory, advisory
securityfocus.com /bid/100823
vdb-entry, third-party-advisory, advisory
nvd.nist.gov /vuln/detail/CVE-2017-12612
advisory
github.com /pypa/advisory-database/tree/main/vulns/pyspark/PYSEC-2017-147.yaml
web

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.