dbcve.org
D5 FirmwareOperating system · Dten

CVE-2019-16273

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-06
Fix available
A fix is available. Upgrade to 1.3.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

DTEN D5 and D7 video conferencing devices before version 1.3.4 expose Android Debug Bridge (adb) without authentication, allowing unauthenticated attackers to gain root shell access and execute arbitrary commands. This also enables covert screen capture of Zoom Client on Windows by issuing commands through the Android OS.

MitigationUpdate DTEN D5 and D7 devices to firmware version 1.3.4 or later. If immediate patching is not possible, disable adb or restrict network access to adb ports (typically TCP 5555).

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
D5 FirmwareOperating system
Affected:< 1.3.4
D7 FirmwareOperating system
Affected:< 1.3.4

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify DTEN device model
    Locate the physical DTEN D5 or D7 video conferencing device on your network or physically inspect it to confirm the model number. Check device labels, management interface, or network inventory records.
    Affected if The device is a DTEN D5 or D7 model.
  2. Check firmware version
    Access the DTEN device admin interface or check the device settings to view the current firmware version. Compare it against the affected version range.
    Affected if The firmware version is below 1.3.4.
  3. Verify adb port exposure
    Perform a network scan of the DTEN device to check if TCP port 5555 (default adb port) is open and accessible. Use a tool like nmap: nmap -p 5555 <device_ip>
    Affected if TCP port 5555 is open and accepting connections from untrusted networks.
  4. Confirm adb service status
    If port 5555 is open, attempt an adb connect to the device (adb connect <device_ip>:5555) from an authorized system to verify the adb service is running without authentication.
    Affected if adb connect succeeds without requiring any authentication credentials.

You are affected if you have a DTEN D5 or D7 device running firmware below version 1.3.4 with adb port 5555 exposed and accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.3.4 or later
Fixed in 1.3.4
Interim mitigation

Update DTEN D5 and D7 devices to firmware version 1.3.4 or later. If immediate patching is not possible, disable adb or restrict network access to adb ports (typically TCP 5555).

Recommended fix High confidence

Firmware 1.3.4 (or any version >= 1.3.4)

  1. Obtain the firmware version 1.3.4 or later from the official DTEN support渠道 (support.dten.com or through your DTEN account)
  2. Access the DTEN device admin interface or follow the manufacturer's documented firmware update procedure
  3. Upload and apply the firmware version 1.3.4 or later to the D5 or D7 device
  4. Verify the device is running firmware version 1.3.4 or later after the update completes
  5. After upgrading, review whether Android Debug Bridge (adb) is needed for ongoing operations; if not required, disable it through device settings or contact DTEN support for guidance

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in D5 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-16273 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-16273 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data