# CVE-2017-12612: Apache Spark Deserialization of Untrusted Data vulnerability

Source: https://junglewise.ai/threats/cve-2017-12612-apache-spark-deserialization-of-untrusted-data-vulnerability  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2017-09-13  
License: CC BY 4.0 with a link back

CVE-2017-12612 · Severity: low · CVSS 3 · Published 2017-09-13

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.

Technologies: [org.apache.spark:spark-core_2.10 (Maven)](https://junglewise.ai/threats/technologies/org-apache-spark-spark-core-2-10), [org.apache.spark:spark-core_2.11 (Maven)](https://junglewise.ai/threats/technologies/org-apache-spark-spark-core-2-11), [pyspark (PyPI)](https://junglewise.ai/threats/technologies/pyspark). Vendors: [Maven](https://junglewise.ai/threats/vendors/maven), [PyPI](https://junglewise.ai/threats/vendors/pypi).

## Quick answers

**Is CVE-2017-12612 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2017-12612 being exploited in the wild.

**How severe is CVE-2017-12612?** Low severity, with a CVSS score of 3, published 13 September 2017.

**Which products and versions are affected?** org.apache.spark:spark-core_2.10 (Maven) ECOSYSTEM:introduced=0,fixed=2.1.2; org.apache.spark:spark-core_2.11 (Maven) ECOSYSTEM:introduced=0,fixed=2.1.2; pyspark (PyPI) ECOSYSTEM:introduced=0,fixed=2.1.2.

**Is there a fix for CVE-2017-12612?** Yes. org.apache.spark:spark-core_2.10 (Maven): upgrade to 2.1.2 or later; org.apache.spark:spark-core_2.11 (Maven): upgrade to 2.1.2 or later; pyspark (PyPI): upgrade to 2.1.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2017-12612?** Check whether you run org.apache.spark:spark-core_2.10 (Maven), org.apache.spark:spark-core_2.11 (Maven) or pyspark (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- org.apache.spark:spark-core_2.10 (Maven): upgrade to 2.1.2 or later

  ```sh
  # set org.apache.spark:spark-core_2.10 to 2.1.2 in your pom.xml or build.gradle
  ```

- org.apache.spark:spark-core_2.11 (Maven): upgrade to 2.1.2 or later

  ```sh
  # set org.apache.spark:spark-core_2.11 to 2.1.2 in your pom.xml or build.gradle
  ```

- pyspark (PyPI): upgrade to 2.1.2 or later

  ```sh
  pip install "pyspark>=2.1.2"
  ```


## Affected products

- org.apache.spark:spark-core_2.10 (Maven) ECOSYSTEM:introduced=0,fixed=2.1.2
- org.apache.spark:spark-core_2.11 (Maven) ECOSYSTEM:introduced=0,fixed=2.1.2
- pyspark (PyPI) ECOSYSTEM:introduced=0,fixed=2.1.2

## Identifiers

- CVE-2017-12612
- GHSA-8rhc-48pp-52gr
- PYSEC-2017-147

## Related threats

- [Apache Spark History Server XSS in job names](https://junglewise.ai/threats/cve-2026-32773-apache-spark-history-server-xss-in-job-names)
- [Apache Spark: Spark History Server Code Execution Vulnerability](https://junglewise.ai/threats/cve-2025-54920-apache-spark-spark-history-server-code-execution-vulnerability)
- [Apache Spark Inadequate Encryption Strength in RPC Communication](https://junglewise.ai/threats/cve-2025-55039-apache-spark-inadequate-encryption-strength-in-rpc-communication)
- [Apache Spark UI vulnerable to Command Injection](https://junglewise.ai/threats/cve-2023-32007-apache-spark-ui-vulnerable-to-command-injection)
- [Apache Spark privilege escalation via classpath injection](https://junglewise.ai/threats/cve-2023-22946-apache-spark-privilege-escalation-via-classpath-injection)