First published: Wed Sep 13 2017(Updated: )
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.1.2, 2.2.0 or later.
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Spark | =1.6.0 | |
Apache Spark | =1.6.1 | |
Apache Spark | =1.6.2 | |
Apache Spark | =1.6.3 | |
Apache Spark | =2.0.0 | |
Apache Spark | =2.0.1 | |
Apache Spark | =2.0.2 | |
Apache Spark | =2.1.0 | |
Apache Spark | =2.1.1 | |
pip/pyspark | <2.1.2 | 2.1.2 |
maven/org.apache.spark:spark-core_2.10 | <2.1.2 | 2.1.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-12612 is classified as a critical vulnerability due to its potential for arbitrary code execution.
To fix CVE-2017-12612, upgrade Apache Spark to version 2.1.2 or later.
Affected versions of Apache Spark include 1.6.0 through 2.1.1.
CVE-2017-12612 can allow an attacker with local access to execute arbitrary code in applications launched via the Spark launcher API.
CVE-2017-12612 is considered a local vulnerability as it requires local user account access to exploit.