# CVE-2020-11614: Supply chain in n/a

> An attacker can execute arbitrary code via man-in-the-middle attacks due to cleartext HTTP updates and lack of file integrity validation in Hero Designer.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** No
- **Published:** 11 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-j8cg-7fhc-xrwv

## What is CVE-2020-11614?

CVE-2020-11614 is a high-severity vulnerability in n/a, published on 11 Jun 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mids' Reborn Hero Designer 2.6.0.7 downloads the update manifest, as well as update files, over cleartext HTTP. Additionally, the application does not perform file integrity validation for files after download. An attacker can perform a man-in-the-middle attack against this connection and replace executable files with malicious versions, which the operating system then executes under the context of the user running Hero Designer.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity), CWE-319 (Cleartext Transmission of Sensitive Information)

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

It affects 1 product.


Products: Mids\' Reborn Hero Designer Project Mids\' Reborn Hero Designer.

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

No fix has been published for CVE-2020-11614 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-11614 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11613](https://insights.sbomify.com/CVE-2020-11613/): Privilege escalation in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11614 is a high-severity vulnerability in n/a, published on 11 Jun 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-11614 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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