Apache Helix: Deserialization vulnerability in Helix workflow and REST
Apache Software Foundation Apache Helix
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.helix:helix-core Maven |
|
|
| org.apache.helix:helix-rest Maven |
|
|
Apache Software Foundation Apache Helix
| Product | Affected | Fixed in |
|---|---|---|
| org.apache.helix:helix-core Maven |
|
|
| org.apache.helix:helix-rest Maven |
|
|
An attacker can use SnakeYAML to deserialize java.net.URLClassLoader and make it load a JAR from a specified URL, and then deserialize javax.script.ScriptEngineManager to load code using that ClassLoader. This unbounded deserialization can likely lead to remote code execution. The code can be run in Helix REST start and Workflow creation.
Affect all the versions lower and include 1.2.0.
Affected products: helix-core, helix-rest
Mitigation: Short term, stop using any YAML based configuration and workflow creation. Long term, all Helix version bumping up to 1.3.0
From the CVE record · apache
Apache Helix has an unbounded YAML deserialization vulnerability in REST start and workflow creation. An attacker can use it to load code from a specified URL, potentially leading to remote code execution. The input does not specify whether authentication or user interaction is required.
Teams running Apache Helix helix-core or helix-rest versions earlier than 1.3.0, including 1.2.0, should check their deployments.