# CVE-2020-11613: Privilege escalation in n/a

> Attackers can escalate privileges by replacing binaries or planting malicious DLLs in the installation folder due to insecure default permissions.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 11 Jun 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-qpq4-373m-q6x8

## What is CVE-2020-11613?

CVE-2020-11613 is a high-severity vulnerability in n/a, published on 11 Jun 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Mids' Reborn Hero Designer 2.6.0.7 has an elevation of privilege vulnerability due to default and insecure permissions being set for the installation folder. By default, the Authenticated Users group has Modify permissions to the installation folder. Because of this, any user on the system can replace binaries or plant malicious DLLs to obtain elevated, or different, privileges, depending on the context of the user that runs the application.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource), CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


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

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

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

## Is CVE-2020-11613 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11614](https://insights.sbomify.com/CVE-2020-11614/): Supply chain in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-11613 is a high-severity vulnerability in n/a, published on 11 Jun 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-11613 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-11613/ (Markdown: https://insights.sbomify.com/CVE-2020-11613/index.md)
```

## Sources

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

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