Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.2

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

CVE-2018-11770GHSA-w4r4-65mg-45x2

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Maven org.apache.spark:spark-core_2.11

    Affected
    >= 1.0.0, <= 2.3.2
    Fixed in
    no fixed version recorded

  • Maven org.apache.spark:spark-core_2.10

    Affected
    >= 1.0.0, <= 2.2.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.2 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS
  • CVE-2018-11770: 66.07% estimated exploitation activity in the next 30 days; percentile 99.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-w4r4-65mg-45x2

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2018-11770

Advisory: org.apache.spark:spark-core_2.10 and org.apache.spark:spark-core_2.11 Improper Authentication vulnerability
IDs: CVE-2018-11770, GHSA-w4r4-65mg-45x2
Record: https://patchnext.com/advisories/cve-2018-11770 (revision 1, source checked 26 Oct 2026, 16:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.spark:spark-core_2.11: affected >= 1.0.0, <= 2.3.2
- Maven org.apache.spark:spark-core_2.10: affected >= 1.0.0, <= 2.2.2

## Suggested inspection (read-only)
- Maven org.apache.spark:spark-core_2.11: check the installed version with your package manager.
- Maven org.apache.spark:spark-core_2.10: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.spark:spark-core_2.11, org.apache.spark:spark-core_2.10.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-w4r4-65mg-45x2 (GitHub-reviewed advisory GHSA-w4r4-65mg-45x2 lists affected ranges: Maven org.apache.spark:spark-core_2.11 >=1.0.0 =1.0.0 <=2.2.2)

Commands are suggestions: review each one before running it.

Loading voting…