CVE-2017-12612

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.7% (52nd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation1% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
53rd
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 13, 2017

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Oct 4, 2026
Patch available.
generic

Pony Mail

https://mail-archives.apache.org/mod_mbox/spark-dev/201709.mbox/%3CCAEccTyy-1yYuhdNgkBUg0sr9NeaZSrBKkBePdTNZbxXZNTAR-g%40mail.gmail.com%3E
generic

CVE-2017-12612 - PSIRT.COM

http://www.securityfocus.com/bid/100823

Affected Packages

(3 across 2 ecosystems)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
org.apache.spark:spark-core_2.100.9.0-incubating ... 2.1.1 (28 versions)
  • every version up to 2.1.2: fixed in 2.1.2
—
org.apache.spark:spark-core_2.111.2.0 ... 2.1.1 (20 versions)
  • every version up to 2.1.2: fixed in 2.1.2
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pyspark2.1.1
  • every version up to 2.1.2: fixed in 2.1.2
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 8× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 157 total refreshes for this CVE.

  1. 2026-10-09 20:02 UTCEPSS rescore
  2. 2026-10-08 16:35 UTCEPSS rescore
  3. 2026-10-08 00:24 UTCOSV refresh
  4. 2026-10-07 23:41 UTCEPSS rescore
  5. 2026-10-06 15:11 UTCEPSS rescore
  6. 2026-10-05 17:38 UTCEPSS rescore
  7. 2026-10-04 23:18 UTCEPSS rescore
  8. 2026-10-03 14:21 UTCEPSS rescore
  9. 2026-09-30 14:58 UTCEPSS rescore
  10. 2026-09-30 09:24 UTCEG score recompute
  11. 2026-09-28 13:45 UTCEPSS rescore
  12. 2026-09-27 13:40 UTCEPSS rescore
  13. 2026-09-26 15:53 UTCEPSS rescore
  14. 2026-09-24 13:59 UTCEPSS rescore
  15. 2026-09-19 15:36 UTCEPSS rescore
  16. 2026-09-18 19:22 UTCEPSS rescore
  17. 2026-09-18 06:36 UTCOSV refresh
  18. 2026-09-17 19:22 UTCEPSS rescore
  19. 2026-09-15 03:05 UTCEPSS rescore
  20. 2026-09-13 16:42 UTCEPSS rescore
  21. 2026-09-12 14:55 UTCEPSS rescore
  22. 2026-09-11 09:31 UTCEPSS rescore
  23. 2026-09-10 09:26 UTCEPSS rescore
  24. 2026-09-07 15:56 UTCEPSS rescore
  25. 2026-09-04 13:56 UTCEPSS rescore
Show 75 more
  1. 2026-09-04 05:01 UTCEPSS rescore
  2. 2026-09-02 14:07 UTCEPSS rescore
  3. 2026-09-01 13:48 UTCEPSS rescore
  4. 2026-09-01 03:31 UTCEPSS rescore
  5. 2026-08-30 19:13 UTCEPSS rescore
  6. 2026-08-30 07:00 UTCOSV refresh
  7. 2026-08-28 21:36 UTCEPSS rescore
  8. 2026-08-27 14:20 UTCEPSS rescore
  9. 2026-08-26 14:41 UTCEPSS rescore
  10. 2026-08-25 13:44 UTCEPSS rescore
  11. 2026-08-24 14:10 UTCEPSS rescore
  12. 2026-08-21 23:44 UTCEPSS rescore
  13. 2026-08-20 22:50 UTCEPSS rescore
  14. 2026-08-19 16:59 UTCEPSS rescore
  15. 2026-08-18 13:43 UTCEPSS rescore
  16. 2026-08-17 13:42 UTCEPSS rescore
  17. 2026-08-16 14:51 UTCEPSS rescore
  18. 2026-08-16 02:10 UTCEPSS rescore
  19. 2026-08-15 01:26 UTCEPSS rescore
  20. 2026-08-13 22:34 UTCOSV refresh
  21. 2026-08-13 21:56 UTCEPSS rescore
  22. 2026-08-09 13:42 UTCEPSS rescore
  23. 2026-08-08 16:32 UTCEPSS rescore
  24. 2026-08-07 16:22 UTCEPSS rescore
  25. 2026-08-06 13:42 UTCEPSS rescore
  26. 2026-08-05 19:12 UTCEPSS rescore
  27. 2026-08-04 15:05 UTCEPSS rescore
  28. 2026-08-04 10:32 UTCEPSS rescore
  29. 2026-08-03 10:30 UTCEPSS rescore
  30. 2026-08-02 02:23 UTCEPSS rescore
  31. 2026-08-01 04:11 UTCEPSS rescore
  32. 2026-07-30 16:24 UTCEPSS rescore
  33. 2026-07-30 01:26 UTCEPSS rescore
  34. 2026-07-29 01:21 UTCOSV refresh
  35. 2026-07-28 15:32 UTCEPSS rescore
  36. 2026-07-26 14:51 UTCEPSS rescore
  37. 2026-07-25 14:13 UTCEPSS rescore
  38. 2026-07-23 14:15 UTCEPSS rescore
  39. 2026-07-23 01:26 UTCEG score recompute
  40. 2026-07-22 22:05 UTCEG score recompute
  41. 2026-07-22 14:04 UTCEPSS rescore
  42. 2026-07-21 15:21 UTCEPSS rescore
  43. 2026-07-21 15:21 UTCEPSS rescore
  44. 2026-07-20 17:04 UTCEPSS rescore
  45. 2026-07-20 17:04 UTCEPSS rescore
  46. 2026-07-19 14:28 UTCEPSS rescore
  47. 2026-07-19 14:28 UTCEPSS rescore
  48. 2026-07-19 02:26 UTCEPSS rescore
  49. 2026-07-19 02:26 UTCEPSS rescore
  50. 2026-07-18 10:00 UTCEPSS rescore
  51. 2026-07-16 16:59 UTCEPSS rescore
  52. 2026-07-16 16:59 UTCEPSS rescore
  53. 2026-07-15 16:54 UTCEPSS rescore
  54. 2026-07-15 16:54 UTCEPSS rescore
  55. 2026-07-15 01:56 UTCEPSS rescore
  56. 2026-07-13 22:26 UTCEPSS rescore
  57. 2026-07-13 06:09 UTCEPSS rescore
  58. 2026-07-12 05:43 UTCEPSS rescore
  59. 2026-07-11 17:52 UTCOSV refresh
  60. 2026-07-11 08:24 UTCEPSS rescore
  61. 2026-07-09 19:06 UTCEPSS rescore
  62. 2026-07-08 15:10 UTCEPSS rescore
  63. 2026-07-07 13:42 UTCEPSS rescore
  64. 2026-07-06 16:24 UTCEPSS rescore
  65. 2026-07-06 02:20 UTCEPSS rescore
  66. 2026-07-05 02:27 UTCEPSS rescore
  67. 2026-07-04 06:28 UTCEPSS rescore
  68. 2026-07-01 15:02 UTCEPSS rescore
  69. 2026-07-01 15:02 UTCEPSS rescore
  70. 2026-06-30 23:19 UTCEPSS rescore
  71. 2026-06-30 23:19 UTCEPSS rescore
  72. 2026-06-29 14:03 UTCEPSS rescore
  73. 2026-06-28 14:04 UTCEPSS rescore
  74. 2026-06-28 04:53 UTCEPSS rescore
  75. 2026-06-27 03:05 UTCEPSS rescore

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2017-12612?
CVE-2017-12612 is a high vulnerability published on September 13, 2017. 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…
When was CVE-2017-12612 disclosed?
CVE-2017-12612 was first published on September 13, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-12612 actively exploited?
CVE-2017-12612 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (53rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-12612?
CVE-2017-12612 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2017-12612?
A fix for CVE-2017-12612 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-12612

Explore →

Is Your Infrastructure Affected by CVE-2017-12612?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs