CVE-2018-11770

MEDIUMNVD 4.29.0▲
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because EPSS predicts 89% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 4.2 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, ghsa, nvd
Weaponized
4.2
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 66%
CISA-KEV: Not listedEPSS: 66%CVSS: 4.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

CVSS v3
4.2
EG Score
9.0(high)
EPSS
99.2%
KEV
Not listed

Published

August 13, 2018

Last Modified

November 21, 2024

References (6)

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
mavenorg.apache.spark:spark-core_2.10—ghsa
mavenorg.apache.spark:spark-core_2.11—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
org.apache.spark:spark-core_2.101.0.0 ... 2.2.2 (30 versions)——
org.apache.spark:spark-core_2.111.2.0 ... 2.3.2 (29 versions)——

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 4× in last 7d / 30× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 08:24 UTCEPSS rescore
  2. 2026-07-09 19:06 UTCEPSS rescore
  3. 2026-07-07 13:42 UTCEPSS rescore
  4. 2026-07-07 13:42 UTCEPSS rescore
  5. 2026-07-05 02:27 UTCEPSS rescore
  6. 2026-07-04 02:56 UTCOSV refresh
  7. 2026-07-02 16:54 UTCEPSS rescore
  8. 2026-07-01 15:03 UTCEPSS rescore
  9. 2026-07-01 15:03 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-30 23:19 UTCEPSS rescore
  12. 2026-06-29 14:03 UTCEPSS rescore
  13. 2026-06-28 04:53 UTCEPSS rescore
  14. 2026-06-28 04:53 UTCEPSS rescore
  15. 2026-06-27 03:06 UTCEPSS rescore
  16. 2026-06-25 13:47 UTCEPSS rescore
  17. 2026-06-25 13:47 UTCEPSS rescore
  18. 2026-06-24 14:02 UTCEPSS rescore
  19. 2026-06-24 14:02 UTCEPSS rescore
  20. 2026-06-23 21:30 UTCEPSS rescore
  21. 2026-06-22 14:23 UTCEPSS rescore
  22. 2026-06-18 17:50 UTCEPSS rescore
  23. 2026-06-18 17:50 UTCEPSS rescore
  24. 2026-06-17 17:50 UTCEPSS rescore
  25. 2026-06-17 17:50 UTCEPSS rescore
Show 19 more
  1. 2026-06-16 17:50 UTCEPSS rescore
  2. 2026-06-16 17:50 UTCEPSS rescore
  3. 2026-06-15 17:45 UTCEPSS rescore
  4. 2026-06-15 14:43 UTCOSV refresh
  5. 2026-06-12 23:09 UTCEPSS rescore
  6. 2026-06-11 13:57 UTCEPSS rescore
  7. 2026-06-10 22:16 UTCEPSS rescore
  8. 2026-06-10 13:19 UTCEPSS rescore
  9. 2026-06-05 22:45 UTCEPSS rescore
  10. 2026-06-05 22:44 UTCEPSS rescore
  11. 2026-06-01 13:49 UTCEPSS rescore
  12. 2026-05-28 04:08 UTCEG score recompute
  13. 2026-05-28 04:08 UTCGHSA enrichment
  14. 2026-05-27 13:38 UTCEPSS rescore
  15. 2026-05-27 13:38 UTCEPSS rescore
  16. 2026-05-26 13:42 UTCEPSS rescore
  17. 2026-05-26 13:42 UTCEPSS rescore
  18. 2026-05-26 07:17 UTCEPSS rescore
  19. 2026-05-26 07:17 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/linux/http/spark_unauth_rce✓ verified
    First seen Dec 12, 2017

    Apache Spark Unauthenticated Command Execution

    Open source ↗

Related CVEs(same product + same CWE)

Same product

2 shown

maven:org.apache.spark:spark-core_2.11

Frequently asked(5)

What is CVE-2018-11770?
CVE-2018-11770 is a medium vulnerability published on August 13, 2018. 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…
When was CVE-2018-11770 disclosed?
CVE-2018-11770 was first published in the National Vulnerability Database on August 13, 2018, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2018-11770 actively exploited?
CVE-2018-11770 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2018-11770?
CVE-2018-11770 has a CVSS v3 base score of 4.2 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
How do I remediate CVE-2018-11770?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2018-11770, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2018-11770

Explore →

Is Your Infrastructure Affected by CVE-2018-11770?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs