Details
-
Bug
-
Status: Resolved
-
Minor
-
Resolution: Fixed
-
None
-
None
Description
There is a remote code execution vulnerability in the Apache Commons collections library (https://issues.apache.org/jira/browse/COLLECTIONS-580) that can be exploited simply by causing malicious data to be deserialized using Java serialization.
As Spark is used in security-conscious environments I think it's worth taking a closer look at how the vulnerability affects Spark. What are the points where Spark deserializes external data? Which are affected by using Kryo instead of Java serialization? What mitigation strategies are available?
If the issue is serious enough but mitigation is possible, it may be useful to post about it on the mailing list or blog.
Thanks!
Attachments
Issue Links
- is duplicated by
-
SPARK-11682 Commons-collections object deserialization may expose remote command execution vulnerability
- Resolved
-
SPARK-19943 commons-collections has vulnerability: CVE-2015-6420
- Resolved
- links to