CVE Tools
Track your stack

CVE-2021-38296

Apache Spark Key Negotiation Vulnerability

No known exploitation. EPSS puts it in the 79th percentile. Fixed in 3.1.3.

CVSS 3.17.5HighEPSS percentile79th1.8% chance in 30 daysCISA KEVNot listedNo confirmed exploitation
No public exploit knownFix3.1.3Upgrade to this build
Check it yourself

Nuclei · 1 templateOpenVAS · 2 checks

e.g. Apache Spark Full Encryption Key Recovery Vulnerability · OID 1.3.6.1.4.1.25623.1.0.106503

Run the check

Published Updated Sources: CVE.org, NVD, GitHub

NVD CVE.org

What to do

Find your product and version, then upgrade to the build on the right.

  • Apache Software Foundation Apache SparkAffected: ≥ up to and including version 3.1.2, ≤ 3.1.2Upgrade to: after 3.1.2Stated by: CVE record
  • Maven org.apache.spark:spark-coreAffected: < 3.1.3Upgrade to: 3.1.3Stated by: GitHub advisory
  • PyPI pysparkAffected: < 3.1.3Upgrade to: 3.1.3Stated by: GitHub advisory

Versions as the sources state them. Full version matrix after sign-in

Check it yourselfA free Nuclei and OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Discuss checks for your systems with a specialist. Scope is agreed before testing.

What it is

From the CVE record

Apache Spark supports end-to-end encryption of RPC connections via "spark.authenticate" and "spark.network.crypto.enabled". In versions 3.1.2 and earlier, it uses a bespoke mutual authentication protocol that allows for full encryption key recovery. After an initial interactive attack, this would allow someone to decrypt plaintext traffic offline. Note that this does not affect security mechanisms controlled by "spark.authenticate.enableSaslEncryption", "spark.io.encryption.enabled", "spark.ssl", "spark.ui.strictTransportSecurity". Update to Apache Spark 3.1.3 or later

In plain language

No plain-language summary for this CVE yet.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS79th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

1.8% chance of exploitation activity in the next 30 days, which ranks it in the 79th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

7 events over 1568 days, from the signal feeds we watch.

  1. OpenVAS check added
  2. Nuclei check added
  3. Patch availablerecord updated
  4. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Scored 7.5 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity NoneNo integrity impact
  • Availability NoneNo availability impact

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

References in the record

And 2 more references. See all after sign-in

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Apache Spark, not every advisory.