# CVE-2019-6005: Auth bypass in firmware version prior to 1300

> Remote attackers can bypass access restrictions on Smart TV Boxes to install arbitrary software or change settings via the Android Debug Bridge port.

- **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:** 12 Sep 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-cjm9-34g2-v82g

## What is CVE-2019-6005?

CVE-2019-6005 is a critical authentication bypass vulnerability in Smart TV Box firmware version prior to 1300, published on 12 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

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

It affects 1 product.


Products: Kddi Smart Tv Box Firmware.

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

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

## Is CVE-2019-6005 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-6005 is a critical authentication bypass vulnerability in Smart TV Box firmware version prior to 1300, published on 12 Sep 2019. 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-6005 in the wild and no public exploit code.

Affected product: Smart TV Box firmware version prior to 1300. 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-6005/ (Markdown: https://insights.sbomify.com/CVE-2019-6005/index.md)
```

## Sources

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

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