CVE-2025-55039

{"id": "CVE-2025-55039", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2025-55039", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "no"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2025-10-15T19:33:07.860034Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 6.5, "attackVector": "NETWORK", "baseSeverity": "MEDIUM", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N", "integrityImpact": "LOW", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "LOW"}, "impactScore": 2.5, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security@apache.org", "affectedData": [{"vendor": "Apache Software Foundation", "product": "Apache Spark", "versions": [{"status": "affected", "version": "3.5.0", "lessThan": "3.5.2", "versionType": "semver"}, {"status": "affected", "version": "0", "lessThan": "3.4.4", "versionType": "semver"}], "packageName": "org.apache.spark:spark-network-common_2.13", "collectionURL": "https://repo.maven.apache.org/maven2", "defaultStatus": "unaffected"}, {"vendor": "Apache Software Foundation", "product": "Apache Spark", "versions": [{"status": "affected", "version": "3.5.0", "lessThan": "3.5.2", "versionType": "semver"}, {"status": "affected", "version": "0", "lessThan": "3.4.4", "versionType": "semver"}], "packageName": "org.apache.spark:spark-network-common_2.12", "collectionURL": "https://repo.maven.apache.org/maven2", "defaultStatus": "unaffected"}]}], "published": "2025-10-15T08:15:38.460", "references": [{"url": "https://lists.apache.org/thread/zrgyy9l85nm2c7vk36vr7bkyorg3w4qq", "tags": ["Mailing List", "Vendor Advisory"], "source": "security@apache.org"}, {"url": "http://www.openwall.com/lists/oss-security/2025/10/14/11", "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Modified", "weaknesses": [{"type": "Secondary", "source": "security@apache.org", "description": [{"lang": "en", "value": "CWE-326"}, {"lang": "en", "value": "CWE-347"}]}], "descriptions": [{"lang": "en", "value": "This issue affects Apache Spark versions before 3.4.4,\u00a03.5.2 and 4.0.0.\n\n\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\n\nTo mitigate this issue, users should either configure spark.network.crypto.cipher to AES/GCM/NoPadding to enable authenticated encryption or\n\nenable SSL encryption by setting spark.ssl.enabled to true, which provides stronger transport security."}, {"lang": "es", "value": "Este problema afecta a las versiones de Apache Spark anteriores a 3.4.4, 3.5.2 y 4.0.0.\n\nLas versiones de Apache Spark anteriores a 4.0.0, 3.5.2 y 3.4.4 utilizan un cifrado de red predeterminado inseguro para la comunicaci\u00f3n RPC entre nodos.\n\nCuando spark.network.crypto.enabled se establece en true (est\u00e1 establecido en false por defecto), pero spark.network.crypto.cipher no se configura expl\u00edcitamente, Spark utiliza por defecto AES en modo CTR (AES/CTR/NoPadding), lo que proporciona cifrado sin autenticaci\u00f3n.\n\nEsta vulnerabilidad permite a un atacante man-in-the-middle modificar el tr\u00e1fico RPC cifrado sin ser detectado al voltear bits en el texto cifrado, comprometiendo potencialmente los mensajes de latido o los datos de la aplicaci\u00f3n y afectando la integridad de los flujos de trabajo de Spark.\n\nPara mitigar este problema, los usuarios deben configurar spark.network.crypto.cipher a AES/GCM/NoPadding para habilitar el cifrado autenticado o habilitar el cifrado SSL estableciendo spark.ssl.enabled en true, lo que proporciona una seguridad de transporte m\u00e1s robusta."}], "lastModified": "2026-10-08T12:10:00.217", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:apache:spark:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "31BCFAC4-6096-41FE-82C7-2B1FEBBA485F", "versionEndExcluding": "3.4.4"}, {"criteria": "cpe:2.3:a:apache:spark:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "C08715D5-2896-4CF9-8908-4780059E738F", "versionEndExcluding": "3.5.2", "versionStartIncluding": "3.5.0"}], "operator": "OR"}]}], "sourceIdentifier": "security@apache.org"}