Description
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
Remediation
References
https://lists.apache.org/thread/70x8fw2gx3g9ty7yk0f2f1dlpqml2smd
https://www.oracle.com/security-alerts/cpujul2022.html
Related Vulnerabilities
CVE-2021-21141 Vulnerability in maven package org.webjars.npm:electron
CVE-2023-48796 Vulnerability in maven package org.apache.dolphinscheduler:dolphinscheduler-api
CVE-2018-11040 Vulnerability in maven package org.springframework:spring-webmvc
CVE-2021-42550 Vulnerability in maven package ch.qos.logback:logback-core
CVE-2019-10277 Vulnerability in maven package hudson.plugins:starteam