# CVE-2020-10513: iCatch DVR - Broken Access Control

> Attackers can remotely manipulate arbitrary files due to broken access control in the iCatch DVR firmware file management interface.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Apr 2020
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-jcjj-hqg4-gr43

## What is CVE-2020-10513?

CVE-2020-10513 is a high-severity missing authorization vulnerability in iCatch Inc. DVR firmware, published on 15 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The file management interface of iCatch DVR firmware before 20200103 contains broken access control which allows the attacker to remotely manipulate arbitrary file.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Icatchinc Dvr Interface.

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

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

## Is CVE-2020-10513 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2020-10513 is a high-severity missing authorization vulnerability in iCatch Inc. DVR firmware, published on 15 Apr 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-10513 in the wild and no public exploit code.

Affected product: iCatch Inc. DVR firmware. 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-10513/ (Markdown: https://insights.sbomify.com/CVE-2020-10513/index.md)
```

## Sources

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

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