From version 1.3.0 onward, Apache Spark's standalone master exposes a REST API for job submission, in addition to the…
Apache Software Foundation · Apache Spark
Apache Spark's standalone master exposes a REST API for job submission (from version 1.3.0 onward) that does not enforce the shared-secret authentication used by spark-submit, so the flaw lies in that REST submission interface. An attacker with network access to the standalone master can run a driver program without authenticating, though they cannot launch executors through this API.
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'.
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 7 years after disclosure. Public exploit code (Metasploit) was available 8 months before disclosure.
- Public exploit codeMetasploit8 mo before
- Disclosedday 0
- First seen exploitedVulnCheck KEV evidence+7 yrs
MITRE ATT&CKA public catalogue of the techniques attackers use, maintained by MITRE. Patchfirst uses it to describe what attackers do with a vulnerability. techniques
No techniques linkedNo ATT&CK techniques are linked to this CVE yet. MITRE CTID has not mapped it, and no report passage in the corpus ties it to a technique.
Am I affected? What do I upgrade to?
From GitHub Security Advisories and OSV2 packages in 1 ecosystem. No single main package: each of these ships the affected code.
- Mavenorg.apache.spark:spark-core_2.11Affected: 1.0.0 through 2.3.2No fixed version published
- Mavenorg.apache.spark:spark-core_2.10Affected: 1.0.0 through 2.2.2No fixed version published