# CVE-2020-3924: TONNET DVR – Firmware Injection

> Attackers can inject commands into patch files to gain unauthorized access to TONNET DVR systems.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 27 Feb 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-xv64-jjpm-mgjv

## What is CVE-2020-3924?

CVE-2020-3924 is a medium-severity command injection vulnerability in TONNET DVR, published on 27 Feb 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

DVR firmware in TAT-76 and TAT-77 series of products, provided by TONNET do not properly verify patch files. Attackers can inject a specific command into a patch file and gain access to the system.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 8 products.


Products: Tonnet Tat-70432n Firmware, Tonnet Tat-71416g1 Firmware, Tonnet Tat-71832g1 Firmware, Tonnet Tat-76104g3 Firmware, Tonnet Tat-76108g3 Firmware, Tonnet Tat-76116g3 Firmware, Tonnet Tat-76132g3 Firmware, Tonnet Tat-77104g1 Firmware.

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

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

## Is CVE-2020-3924 being exploited?

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

## Other vulnerabilities in TONNET DVR

- [CVE-2020-3923](https://insights.sbomify.com/CVE-2020-3923/): TONNET DVR – Broken Access Control (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-3924 is a medium-severity command injection vulnerability in TONNET DVR, published on 27 Feb 2020. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2020-3924 in the wild and no public exploit code.

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

## Sources

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

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