In all versions of Apache Spark, its standalone resource manager accepts code to execute on a 'master' host, that then runs that code on 'worker' hosts. The master itself does not, by design, execute user code. A specially-crafted request to the master can, however, cause the master to execute code too. Note that this does not affect standalone clusters with authentication enabled. While the master host typically has less outbound access to other resources than a worker, the execution of code on the master is nevertheless unexpected.
References
Link | Resource |
---|---|
https://lists.apache.org/thread.html/341c3187f15cdb0d353261d2bfecf2324d56cb7db1339bfc7b30f6e5@%3Cdev.spark.apache.org%3E | Mailing List Vendor Advisory |
http://www.securityfocus.com/bid/105976 | Third Party Advisory VDB Entry |
https://security.gentoo.org/glsa/201903-21 | Third Party Advisory |
https://www.oracle.com/security-alerts/cpujul2020.html |
Configurations
Information
Published : 2018-11-19 06:29
Updated : 2020-08-24 10:37
NVD link : CVE-2018-17190
Mitre link : CVE-2018-17190
JSON object : View
CWE
Products Affected
apache
- spark