# CVE-2019-16273: Auth bypass in n/a

> Unauthenticated attackers can gain root shell access via ADB on DTEN devices, enabling arbitrary code execution and system administration.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Jan 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-x7cq-cqf3-v9jr

## What is CVE-2019-16273?

CVE-2019-16273 is a critical authentication bypass vulnerability in n/a, published on 6 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

DTEN D5 and D7 before 1.3.4 devices allow unauthenticated root shell access through Android Debug Bridge (adb), leading to arbitrary code execution and system administration. Also, this provides a covert ability to capture screen data from the Zoom Client on Windows by executing commands on the Android OS.

## Which versions are affected by CVE-2019-16273?

It affects 2 products.


Products: Dten D5 Firmware, Dten D7 Firmware.

## How do I fix CVE-2019-16273?

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

## Is CVE-2019-16273 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16272](https://insights.sbomify.com/CVE-2019-16272/): Security feature bypass in n/a (critical 9.8)
- [CVE-2019-16274](https://insights.sbomify.com/CVE-2019-16274/): Information disclosure in n/a (high 7.5)
- [CVE-2019-16271](https://insights.sbomify.com/CVE-2019-16271/): Missing authorization in n/a (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-16273 and fix it if it is affected.

What it is: CVE-2019-16273 is a critical authentication bypass vulnerability in n/a, published on 6 Jan 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-2019-16273 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-2019-16273/ (Markdown: https://insights.sbomify.com/CVE-2019-16273/index.md)
```

## Sources

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

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