# CVE-2020-12837: File upload in n/a

> Attackers can upload malicious files disguised as PNG images to the garage door interface, potentially leading to code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Sep 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-wcpp-58jv-4c64

## What is CVE-2020-12837?

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

### Official description

ismartgate PRO 1.5.9 is vulnerable to malicious file uploads via the form for uploading images to garage doors. The magic bytes of PNG must be used.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

It affects 1 product.


Products: Gogogate Ismartgate Pro Firmware.

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

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

## Is CVE-2020-12837 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12838](https://insights.sbomify.com/CVE-2020-12838/): Code injection in n/a (critical 9.8)
- [CVE-2020-12839](https://insights.sbomify.com/CVE-2020-12839/): Code injection in n/a (critical 9.8)
- [CVE-2020-12842](https://insights.sbomify.com/CVE-2020-12842/): Code injection in n/a (critical 9.8)
- [CVE-2020-12843](https://insights.sbomify.com/CVE-2020-12843/): File upload in n/a (critical 9.8)
- [CVE-2020-12282](https://insights.sbomify.com/CVE-2020-12282/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12837 is a high-severity vulnerability in n/a, published on 24 Sep 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-12837 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-12837/ (Markdown: https://insights.sbomify.com/CVE-2020-12837/index.md)
```

## Sources

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

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