~ / search / GHSA-6p6v-m64v-jx8q

GHSA-6p6v-m64v-jx8q

Apache Spark has Inadequate Encryption Strength

Source: GitHub Advisory Database (reviewed) Low CVE-2025-55039

Packages

EcosystemPackageAffectedFixed in
Maven org.apache.spark:spark-network-common_2.13 >= 3.5.0, < 3.5.2 3.5.2
Maven org.apache.spark:spark-network-common_2.13 < 3.4.4 3.4.4
Maven org.apache.spark:spark-network-common_2.12 < 3.4.4 3.4.4
Maven org.apache.spark:spark-network-common_2.12 >= 3.5.0, < 3.5.2 3.5.2
PyPI pyspark < 3.4.4 3.4.4
PyPI pyspark >= 3.5.0, < 3.5.2 3.5.2

Details

As written in the advisory (Markdown source, shown as plain text).

This issue affects Apache Spark versions before 3.4.4, 3.5.2 and 4.0.0. Apache Spark versions before 4.0.0, 3.5.2 and 3.4.4 use an insecure default network encryption cipher for RPC communication between nodes. When spark.network.crypto.enabled is set to true (it is set to false by default), but spark.network.crypto.cipher is not explicitly configured, Spark defaults to AES in CTR mode (AES/CTR/NoPadding), which provides encryption without authentication. This vulnerability allows a man-in-the-middle attacker to modify encrypted RPC traffic undetected by flipping bits in ciphertext, potentially compromising heartbeat messages or application data and affecting the integrity of Spark workflows. To mitigate this issue, users should either configure spark.network.crypto.cipher to AES/GCM/NoPadding to enable authenticated encryption or enable SSL encryption by setting spark.ssl.enabled to true, which provides stronger transport security.

References

External links from the advisory. They lead to third-party sites.