dbcve.org
Smart Tv Box FirmwareOperating system · Kddi

CVE-2019-6005

CRITICAL · 9.8 CVSS v3.1 Published 2019-09-12
Fix available
A fix is available. Upgrade to 1300 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
Smart TV Box firmware version prior to 1300 allows remote attackers to bypass access restriction to conduct arbitrary operations on the device without user's intent, such as installing arbitrary software or changing the device settings via Android Debug Bridge port 5555/TCP.

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

Android Debug Bridge (ADB) port 5555/TCP is exposed without authentication on Smart TV Box firmware versions prior to 1300, allowing remote unauthenticated attackers to bypass access restrictions and execute arbitrary commands, install software, or modify device settings.

MitigationUpdate firmware to version 1300 or later, disable ADB debugging, and ensure port 5555/TCP is not exposed to untrusted networks or implement network segmentation and firewall rules as compensating controls.

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
Smart Tv Box FirmwareOperating system
Affected:< 1300

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 device model
    Check the device label, system settings, or boot logs to confirm the device is a Kddi Smart TV Box
    Affected if Device is not a Kddi Smart TV Box (not affected by this specific CVE)
  2. Check firmware version
    Access device settings > system information or run 'getprop ro.build.version.incremental' or 'getprop ro.product.version' via ADB or check in settings menu
    Affected if Firmware version is below 1300 (e.g., 1200, 1100, etc.)
  3. Verify port 5555 is listening
    Run 'netstat -an | grep 5555' or 'nmap -p 5555 <device_ip>' from a network-connected host, or 'ss -tlnp | grep 5555' on the device itself
    Affected if Port 5555/TCP is open and listening on the device
  4. Confirm ADB debugging is enabled
    Check device developer settings or run 'getprop persist.adb.enabled' or 'getprop ro.adb.secure' on the device
    Affected if ADB debugging is turned on (not disabled)
  5. Check network exposure of port 5555
    Test if port 5555 is reachable from untrusted networks using 'nc -zv <device_ip> 5555' or by attempting an ADB connection from an external host
    Affected if Port 5555 is accessible from outside the trusted local network

User is affected if the device is a Kddi Smart TV Box with firmware below version 1300 AND port 5555/TCP is open and exposed to 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 1300 or later
Fixed in 1300
Interim mitigation

Update firmware to version 1300 or later, disable ADB debugging, and ensure port 5555/TCP is not exposed to untrusted networks or implement network segmentation and firewall rules as compensating controls.

Recommended fix High confidence

Firmware version 1300

  1. Check the current firmware version of the Smart TV Box device
  2. Download firmware version 1300 or later from the official vendor support site
  3. Update the device firmware to version 1300 or newer following the vendor's standard firmware update procedure
  4. Verify the firmware update was successful by checking the device settings or version information
  5. As an additional security measure, verify that the Android Debug Bridge (ADB) port 5555/TCP is disabled or properly firewalled if not required for legitimate administrative purposes

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

Fix this in Smart Tv Box Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $3,020
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-6005 — 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-6005 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