CVE-2021-38296: PYSEC-2022-186 - Apache Spark supports end-to-end encryption of RPC connections via "spark.authenticate" and "spark.network.crypto.enabled". In versions 3.1.
CVE-2021-38296 · Severity: low · CVSS 3.1 · Published 2022-03-10
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
Yes. org.apache.spark:spark-core (Maven): upgrade to 3.1.3 or later; pyspark (PyPI): upgrade to 3.1.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2021-38296?
Check whether you run org.apache.spark:spark-core (Maven) or pyspark (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
org.apache.spark:spark-core (Maven): upgrade to 3.1.3 or later
# set org.apache.spark:spark-core to 3.1.3 in your pom.xml or build.gradle