# CVE-2023-38647: Apache Helix: Deserialization vulnerability in Helix workflow and REST

> An attacker can achieve remote code execution in Apache Helix by exploiting unsafe deserialization in workflow and REST components.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 26 Jul 2023
- **Updated:** 2 Oct 2024
- **Also known as:** GHSA-jhcr-hph9-g7wm

## What is CVE-2023-38647?

CVE-2023-38647 is a critical unsafe deserialization vulnerability in Apache Helix, published on 26 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2023-38647?

4 open source packages ship an affected version, including org.apache.helix:helix-core and org.apache.helix:helix-rest. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.helix:helix-core` | Maven | All versions | 1.3.0 |
| `org.apache.helix:helix-core` | Maven | All versions | 1.3.0 |
| `org.apache.helix:helix-rest` | Maven | All versions | 1.3.0 |
| `org.apache.helix:helix-rest` | Maven | All versions | 1.3.0 |

Products: Apache Helix.

## How do I fix CVE-2023-38647?

Upgrade org.apache.helix:helix-core to 1.3.0 or later.

## Is CVE-2023-38647 being exploited?

There is no known exploitation of CVE-2023-38647 in the wild and no public exploit code.

## Other vulnerabilities in Apache Helix

- [CVE-2026-57111](https://insights.sbomify.com/CVE-2026-57111/): Apache Helix REST: Permissive CORS Configuration in REST API Allows Unrestricted Cross-Origin (high 7.5)
- [CVE-2024-22281](https://insights.sbomify.com/CVE-2024-22281/): Apache Helix Front (UI): Helix front hard-coded secret in the express-session (high 7.5)
- [CVE-2022-47500](https://insights.sbomify.com/CVE-2022-47500/): Apache Helix: Open redirect (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-38647 and fix it if it is affected.

What it is: CVE-2023-38647 is a critical unsafe deserialization vulnerability in Apache Helix, published on 26 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-38647 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.helix:helix-core (Maven): affected all versions; fixed in 1.3.0
- org.apache.helix:helix-core (Maven): affected all versions; fixed in 1.3.0
- org.apache.helix:helix-rest (Maven): affected all versions; fixed in 1.3.0
- org.apache.helix:helix-rest (Maven): affected all versions; fixed in 1.3.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-38647/ (Markdown: https://insights.sbomify.com/CVE-2023-38647/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-38647
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-38647
- OSV: https://osv.dev/vulnerability/CVE-2023-38647

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-38647/
Summaries are generated and may contain mistakes; the official description above is the record.