CVE-2017-12612: Apache Spark Unsafe Deserialization Vulnerability
Summary
CVE-2017-12612: Apache Spark Deserialization of Untrusted Data vulnerability. Affects org.apache.spark:spark-core_2.11 versions < 2.1.2. Fixed in 2.1.2. How to fix ↓
Also tracked for
- pyspark · PyPI
The same CVE-2017-12612 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Apache Spark is an open-source distributed computing system used for big data processing and analytics. It provides a programming model and an execution engine for processing large datasets. The spark-core package is a fundamental component of Apache Spark, providing core functionality and APIs for Spark applications. However, versions 1.6.0 to 2.1.1 of spark-core_2.10 and spark-core_2.11 are vulnerable to an unsafe deserialization vulnerability.
Vulnerability Detail
The launcher API in Apache Spark versions 1.6.0 to 2.1.1 performs unsafe deserialization of data received by its socket. This vulnerability allows an attacker with access to any user account on the local machine to execute arbitrary code. Applications launched programmatically using the launcher API are potentially vulnerable. However, applications run by spark-submit or spark-shell are not affected. The attacker can execute code as the user who ran the Spark application.
How To Fix
Minimum fixed version
2.1.2
This is the first release that contains the fix.
Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. Updating to the patched versions is the recommended solution.
Conclusion
The Apache Spark Unsafe Deserialization Vulnerability (CVE-2017-12612) is a high severity vulnerability that affects versions 1.6.0 to 2.1.1 of spark-core_2.10 and spark-core_2.11. It allows an attacker with access to a user account on the local machine to execute arbitrary code. Users are strongly advised to update to Apache Spark version 2.1.2, 2.2.0, or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for org.apache.spark:spark-core_2.11 →
FAQ
Versions 1.6.0 to 2.1.1 of spark-core_2.10 and spark-core_2.11 are affected.
No, the attacker needs access to a user account on the local machine to exploit this vulnerability.
No, this vulnerability only affects applications launched programmatically using the launcher API.
An attacker can execute arbitrary code as the user who ran the Spark application, potentially leading to unauthorized access, data manipulation, or system compromise.
There is no known exploit available for this vulnerability at the time of writing.
Related vulnerabilities
Recent vulnerabilities recorded for org.apache.spark:spark-core_2.11.
