# CVE-2020-1964: Deserialization of Untrusted Data in Apache Heron

> Remote attackers can execute arbitrary code by exploiting unsafe YAML deserialization in Apache Heron.

- **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:** 16 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hjgm-f7vx-m5g7

## What is CVE-2020-1964?

CVE-2020-1964 is a critical unsafe deserialization vulnerability in Apache Heron, published on 16 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

It was noticed that Apache Heron 0.20.2-incubating, Release 0.20.1-incubating, and Release v-0.20.0-incubating does not configure its YAML parser to prevent the instantiation of arbitrary types, resulting in a remote code execution vulnerabilities (CWE-502: Deserialization of Untrusted Data).

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2020-1964?

2 open source packages ship an affected version, including org.apache.heron:heron-simulator. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.heron:heron-simulator` | Maven | From 0.20.0-incubating | 0.20.3-incubating |
| `org.apache.heron:heron-simulator` | Maven | From 0.20.0-incubating | 0.20.3-incubating |

Products: Apache Heron.

## How do I fix CVE-2020-1964?

Upgrade org.apache.heron:heron-simulator to 0.20.3-incubating or later.

## Is CVE-2020-1964 being exploited?

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

## Other vulnerabilities in Apache Heron

- [CVE-2021-42010](https://insights.sbomify.com/CVE-2021-42010/): CRLF log injection (critical 9.8)
- [CVE-2018-11789](https://insights.sbomify.com/CVE-2018-11789/): Path traversal in Apache Incubator Heron (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-1964 and fix it if it is affected.

What it is: CVE-2020-1964 is a critical unsafe deserialization vulnerability in Apache Heron, published on 16 Apr 2020. 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-2020-1964 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.heron:heron-simulator (Maven): affected from 0.20.0-incubating; fixed in 0.20.3-incubating
- org.apache.heron:heron-simulator (Maven): affected from 0.20.0-incubating; fixed in 0.20.3-incubating

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-2020-1964/ (Markdown: https://insights.sbomify.com/CVE-2020-1964/index.md)
```

## Sources

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

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