# CVE-2020-12734: Missing authorization in n/a

> Remote attackers can modify device network settings and demand ransom due to missing authorization and lack of factory reset functionality.

- **Severity:** High 8.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Jul 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-4v8j-8w8m-gj44

## What is CVE-2020-12734?

CVE-2020-12734 is a high-severity missing authorization vulnerability in n/a, published on 15 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

DEPSTECH WiFi Digital Microscope 3 allows remote attackers to change the SSID and password, and demand a ransom payment from the rightful device owner, because there is no way to reset to Factory Default settings.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Depstech Wifi Digital Microscope 3 Firmware.

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

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

## Is CVE-2020-12734 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-12733](https://insights.sbomify.com/CVE-2020-12733/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2020-12732](https://insights.sbomify.com/CVE-2020-12732/): Hardcoded credentials in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2020-12734 is a high-severity missing authorization vulnerability in n/a, published on 15 Jul 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-12734 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-12734/ (Markdown: https://insights.sbomify.com/CVE-2020-12734/index.md)
```

## Sources

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

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