CVE-2020-9480PYSEC-2020-95BIT-SPARK-2020-9480GHSA-WGX7-JWWM-CGJV
In Apache Spark 2.4.5 and earlier, a standalone resource manager's master may be configured to require authentication (spark.authenticate) v
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 2.4.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub, 1 Nuclei template
Summary
In Apache Spark 2.4.5 and earlier, a standalone resource manager's master may be configured to require authentication (spark.authenticate) via a shared secret. When enabled, however, a specially-crafted RPC to the master can succeed in starting an application's resources on the Spark cluster, even without the shared key. This can be leveraged to execute shell commands on the host machine. This does not affect Spark clusters using other resource managers (YARN, Mesos, etc).
Timeline
- CVE published
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- Apache Software Foundation Apache Spark
Version range not reported
- pysparkPyPI
fixed in 2.4.6
- org.apache.spark:spark-parent_2.11Maven
fixed in 2.4.6
References 8
spark.apache.org
lists.apache.org
- thread.html/r03ad9fe7c07d6039fba9f2152d345274473cb0af3d8a4794a6645f4b@<user.spark.apache.org>
- thread.html/ree9e87aae81852330290a478692e36ea6db47a52a694545c7d66e3e2@<dev.spark.apache.org>
- thread.html/rb3956440747e41940d552d377d50b144b60085e7ff727adb0e575d8d@<commits.submarine.apache.org>
- thread.html/ra0e62a18ad080c4ce6df5e0202a27eaada75222761efc3f7238b5a3b@<commits.doris.apache.org>