CVE-2018-17190
Description
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Apache Spark standalone master can be tricked into executing arbitrary code via a specially-crafted request, bypassing the intended design that only workers run user code.
Vulnerability
In all versions of Apache Spark, the standalone resource manager accepts code submitted to the 'master' host for distribution to 'worker' hosts. By design, the master itself does not execute user code; however, a specially-crafted request can cause the master to execute code as well. This affects all versions of Apache Spark (e.g., spark-core_2.10 and spark-core_2.11). Clusters with authentication enabled are not affected [1] [2].
Exploitation
An attacker must be able to send a specially-crafted request to the Spark standalone master. No authentication or special privileges are required if the cluster is not configured with authentication. The attacker crafts a specific request that tricks the master into executing code intended for workers [1].
Impact
Successful exploitation allows the attacker to execute arbitrary code on the master host. While the master typically has less outbound access to other resources compared to a worker, code execution on the master is unexpected and could lead to further compromise of the cluster or sensitive data [1].
Mitigation
Enable authentication on the Spark standalone cluster. This is the recommended workaround and completely prevents exploitation. As of the last advisory, no fixed version has been announced; upgrading to a patched version is not available. The vulnerability is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog. Users should monitor Apache Spark releases for a fix [1] [2].
AI Insight generated on May 22, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
org.apache.spark:spark-core_2.11Maven | >= 0 | — |
org.apache.spark:spark-core_2.10Maven | >= 0 | — |
Affected products
3- ghsa-coords2 versions
>= 0+ 1 more
- (no CPE)range: >= 0
- (no CPE)range: >= 0
- Apache Software Foundation/Apache Sparkv5Range: All versions
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
7- github.com/advisories/GHSA-phg2-9c5g-m4q7ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2018-17190ghsaADVISORY
- security.gentoo.org/glsa/201903-21ghsavendor-advisoryx_refsource_GENTOOWEB
- www.securityfocus.com/bid/105976ghsavdb-entryx_refsource_BIDWEB
- lists.apache.org/thread.html/341c3187f15cdb0d353261d2bfecf2324d56cb7db1339bfc7b30f6e5%40%3Cdev.spark.apache.org%3Emitrex_refsource_MISC
- lists.apache.org/thread.html/341c3187f15cdb0d353261d2bfecf2324d56cb7db1339bfc7b30f6e5@%3Cdev.spark.apache.org%3EghsaWEB
- www.oracle.com/security-alerts/cpujul2020.htmlghsax_refsource_MISCWEB
News mentions
0No linked articles in our index yet.