CVE-2018-11770
Description
From version 1.3.0 onward, Apache Spark's standalone master exposes a REST API for job submission, in addition to the submission mechanism used by spark-submit. In standalone, the config property 'spark.authenticate.secret' establishes a shared secret for authenticating requests to submit jobs via spark-submit. However, the REST API does not use this or any other authentication mechanism, and this is not adequately documented. In this case, a user would be able to run a driver program without authenticating, but not launch executors, using the REST API. This REST API is also used by Mesos, when set up to run in cluster mode (i.e., when also running MesosClusterDispatcher), for job submission. Future versions of Spark will improve documentation on these points, and prohibit setting 'spark.authenticate.secret' when running the REST APIs, to make this clear. Future versions will also disable the REST API by default in the standalone master by changing the default value of 'spark.master.rest.enabled' to 'false'.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Apache Spark standalone REST API for job submission lacks authentication, allowing unauthenticated driver submission.
Vulnerability
Apache Spark's standalone master exposes a REST API for job submission from version 1.3.0 onward [1]. The REST API does not use the spark.authenticate.secret or any other authentication mechanism, unlike the spark-submit method [2]. This affects all versions from 1.3.0 to at least 2.4.x (as of disclosure) [3].
Exploitation
An attacker with network access to the standalone master's REST endpoint can submit driver programs without authentication [1]. The REST API is also used by Mesos when running in cluster mode (via MesosClusterDispatcher) [2]. However, the attacker cannot launch executors through this API [2].
Impact
Successful exploitation allows an attacker to run arbitrary driver code on the Spark cluster [1]. This can lead to resource consumption, information disclosure, or further compromise depending on the cluster configuration [3]. The attacker gains the ability to execute code within the Spark driver's security context [2].
Mitigation
As of the advisory date (August 2018), no patch was available, but future Spark versions (2.4.0 and later) disable the REST API by default by setting spark.master.rest.enabled to false [2]. Administrators should explicitly disable the REST API or use network controls (firewalls, authentication proxies) to restrict access to trusted networks [1]. Avoid setting spark.authenticate.secret when the REST API is enabled [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 | >= 1.0.0, <= 2.3.2 | — |
org.apache.spark:spark-core_2.10Maven | >= 1.0.0, <= 2.2.2 | — |
Affected products
3- ghsa-coords2 versions
>= 1.0.0, <= 2.2.2+ 1 more
- (no CPE)range: >= 1.0.0, <= 2.2.2
- (no CPE)range: >= 1.0.0, <= 2.3.2
- Apache Software Foundation/Apache Sparkv5Range: 1.3.0
Patches
0No patches discovered yet.
Vulnerability mechanics
AI mechanics synthesis has not run for this CVE yet.
References
7- github.com/advisories/GHSA-w4r4-65mg-45x2ghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2018-11770ghsaADVISORY
- www.securityfocus.com/bid/105097mitrevdb-entryx_refsource_BID
- lists.apache.org/thread.html/bd8e51314041451a2acd720e9223fc1c15a263ccacb396a75b1fc485%40%3Cdev.spark.apache.org%3Eghsamailing-listx_refsource_MLISTWEB
- lists.apache.org/thread.html/bd8e51314041451a2acd720e9223fc1c15a263ccacb396a75b1fc485@%3Cdev.spark.apache.org%3EghsaWEB
- spark.apache.org/security.htmlghsax_refsource_CONFIRMWEB
- web.archive.org/web/20200227114942/http://www.securityfocus.com/bid/105097ghsaWEB
News mentions
0No linked articles in our index yet.