First published: Thu Mar 10 2022(Updated: )
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
Credit: security@apache.org security@apache.org
Affected Software | Affected Version | How to fix |
---|---|---|
Apache Spark | <3.1.3 | |
Oracle Financial Services Crime And Compliance Management Studio | =8.0.8.2.0 | |
Oracle Financial Services Crime And Compliance Management Studio | =8.0.8.3.0 | |
pip/pyspark | <3.1.3 | 3.1.3 |
maven/org.apache.spark:spark-core | <3.1.3 | 3.1.3 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-38296 is a vulnerability in Apache Spark that allows for full encryption key recovery after an initial interactive attack.
CVE-2021-38296 has a severity rating of 7.5 (high).
Apache Spark versions up to 3.1.3 and Oracle Financial Services Crime And Compliance Management Studio versions 8.0.8.2.0 and 8.0.8.3.0 are affected by CVE-2021-38296.
To fix CVE-2021-38296, update to a version of Apache Spark that is later than 3.1.3 or update to a version of Oracle Financial Services Crime And Compliance Management Studio that is later than 8.0.8.3.0.
You can find more information about CVE-2021-38296 in the Apache Spark mailing list and the Oracle Security Alerts page.