CVE-2017-12612: High severity Apache Spark vulnerability
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.
Other sources
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-12612?
CVE-2017-12612 is classified as a critical vulnerability due to its potential for arbitrary code execution.
How do I fix CVE-2017-12612?
To fix CVE-2017-12612, upgrade Apache Spark to version 2.1.2 or later.
Which versions of Apache Spark are affected by CVE-2017-12612?
Affected versions of Apache Spark include 1.6.0 through 2.1.1.
What impact does CVE-2017-12612 have on applications?
CVE-2017-12612 can allow an attacker with local access to execute arbitrary code in applications launched via the Spark launcher API.
Is CVE-2017-12612 a local or remote vulnerability?
CVE-2017-12612 is considered a local vulnerability as it requires local user account access to exploit.