CVE-2018-11770: Medium severity apache spark vulnerability

Published Aug 13, 2018
·
Updated

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 2.4.x 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'.

Other sources

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'.

Affected Software

4 affected components
Apache Spark>=1.3.0
Apache Spark>=1.3.0<2.4.0
maven/org.apache.spark:spark-core_2.10>=1.0.0<=2.2.2
maven/org.apache.spark:spark-core_2.11>=1.0.0<=2.3.2

Event History

Aug 13, 2018
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
DescriptionWeakness
Nov 9, 2018
Advisory Published
via GitHub·05:41 PM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is CVE-2018-11770?

CVE-2018-11770 is a vulnerability in Apache Spark's standalone master that exposes a REST API for job submission, allowing unauthorized access to submit jobs.

2

How does CVE-2018-11770 affect Apache Spark?

CVE-2018-11770 affects Apache Spark from version 1.3.0 onward, where the standalone master exposes a REST API for job submission.

3

What is the severity of CVE-2018-11770?

CVE-2018-11770 has a severity rating of medium with a severity value of 4.2.

4

What is the Common Weakness Enumeration (CWE) ID of CVE-2018-11770?

The CWE ID of CVE-2018-11770 is CWE-287.

5

How can I mitigate CVE-2018-11770?

To mitigate CVE-2018-11770, ensure that the 'spark.authenticate.secret' configuration property is properly set to establish a shared secret for authenticating requests to submit jobs via the REST API.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203