Skip to content
Fencer Intel
medium 4.2

CVE-2018-11770 json

org.apache.spark:spark-core_2.10 and org.apache.spark:spark-core_2.11 Improper Authentication vulnerability

published 8y ago modified 4mo ago also GHSA-w4r4-65mg-45x2 , EUVD-2018-0781

cvss
4.2
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
66.1%
EPSS 66.1% chance of exploitation in 30 days, percentile 99.2%
public exploits
1
Metasploit

Summary

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

Patch / fix

  • Apache Software Foundation Apache Spark 2.4.0

Is CVE-2018-11770 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-11770 updated cvss 6.5

spark: Missing authentication allows users to run driver programs via the REST API

  • Red Hat Fuse 7 spark Red Hat JBoss Fuse 6 spark
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. First public exploit (Metasploit exploit/linux/http/spark_unauth_rce)
  2. Published

Exploit prediction

66.07% chance of exploitation in the next 30 days, higher than 99.2% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

CVSS scores

assigned by version score vector
NVD 3.1 4.2 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
NVD 2.0 4.9 AV:N/AC:M/Au:S/C:P/I:P/A:N
GitHub 3.1 4.2 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.spark:spark-core_2.11
>=1.0.0, <=2.3.2
 no fix listed
maven org.apache.spark:spark-core_2.10
>=1.0.0, <=2.2.2
 no fix listed

Affected products

  • Apache Software Foundation Apache Spark

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.