pyspark
Affected
- introduced
0, fixed3.4.4, introduced3.5.0, fixed3.5.2(ecosystem)
Fixed versions
3.4.4, 3.5.2
Fix
- Fixed version
3.4.4pip install --upgrade pyspark==3.4.4 - Fixed version
3.5.2pip install --upgrade pyspark==3.5.2
Advisory
Also known as: CVE-2025-55039, GHSA-6p6v-m64v-jx8q
The record has no summary.
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.
Medium Basis: CVSS v3 score 6.5, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
0, fixed 3.4.4, introduced 3.5.0, fixed 3.5.2 (ecosystem)3.4.4, 3.5.2
3.4.4pip install --upgrade pyspark==3.4.43.5.2pip install --upgrade pyspark==3.5.2Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: PyPA Advisory Database · CC BY 4.0