{"items":[{"id":"NVI-00018426","kind":"vulnerability","title":"Apache Spark has Inadequate Encryption Strength","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-6p6v-m64v-jx8q","CVE-2025-55039"],"plain_summary":"GitHub lists this reviewed advisory for org.apache.spark:spark-network-common_2.13, org.apache.spark:spark-network-common_2.13, org.apache.spark:spark-network-common_2.12, org.apache.spark:spark-network-common_2.12, pyspark. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-21784d498d9f8f3c5297c539da39d60f"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-21784d498d9f8f3c5297c539da39d60f","url":"https://github.com/advisories/GHSA-6p6v-m64v-jx8q","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-6p6v-m64v-jx8q","publisher":"GitHub Advisory Database","observed_at":"2026-11-07T00:52:42.537Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-21784d498d9f8f3c5297c539da39d60f"],"technology":"org.apache.spark:spark-network-common_2.13","known_exclusions":[],"conditions_summary":"This issue affects Apache Spark versions before  3.4.4, 3.5.2 and 4.0.0.\n\nApache 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.\n\nWhen 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.\n\nThis 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.\n\nTo 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.","public_affected_ranges":[">= 3.5.0, < 3.5.2"]},{"certainty":"source_listed","source_ids":["sr-21784d498d9f8f3c5297c539da39d60f"],"technology":"org.apache.spark:spark-network-common_2.13","known_exclusions":[],"conditions_summary":"This issue affects Apache Spark versions before  3.4.4, 3.5.2 and 4.0.0.\n\nApache 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.\n\nWhen 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.\n\nThis 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.\n\nTo 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.","public_affected_ranges":["< 3.4.4"]},{"certainty":"source_listed","source_ids":["sr-21784d498d9f8f3c5297c539da39d60f"],"technology":"org.apache.spark:spark-network-common_2.12","known_exclusions":[],"conditions_summary":"This issue affects Apache Spark versions before  3.4.4, 3.5.2 and 4.0.0.\n\nApache 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.\n\nWhen 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.\n\nThis 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.\n\nTo 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.","public_affected_ranges":["< 3.4.4"]},{"certainty":"source_listed","source_ids":["sr-21784d498d9f8f3c5297c539da39d60f"],"technology":"org.apache.spark:spark-network-common_2.12","known_exclusions":[],"conditions_summary":"This issue affects Apache Spark versions before  3.4.4, 3.5.2 and 4.0.0.\n\nApache 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.\n\nWhen 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.\n\nThis 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.\n\nTo 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.","public_affected_ranges":[">= 3.5.0, < 3.5.2"]},{"certainty":"source_listed","source_ids":["sr-21784d498d9f8f3c5297c539da39d60f"],"technology":"pyspark","known_exclusions":[],"conditions_summary":"This issue affects Apache Spark versions before  3.4.4, 3.5.2 and 4.0.0.\n\nApache 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.\n\nWhen 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.\n\nThis 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.\n\nTo 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.","public_affected_ranges":[">= 0, < 3.4.4"]},{"certainty":"source_listed","source_ids":["sr-21784d498d9f8f3c5297c539da39d60f"],"technology":"pyspark","known_exclusions":[],"conditions_summary":"This issue affects Apache Spark versions before  3.4.4, 3.5.2 and 4.0.0.\n\nApache 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.\n\nWhen 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.\n\nThis 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.\n\nTo 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.","public_affected_ranges":[">= 3.5.0, < 3.5.2"]}],"null_published_at":"2026-11-07T07:07:39.835Z","source_updated_at":"2026-06-08T19:46:18.000Z","source_disclosed_at":"2025-10-15T09:30:17.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-07T00:52:42.537Z"}],"next_cursor":null,"snapshot_revision":"42594"}