# CVE-2016-6553: Nuuo NT-4040 Titan, firmware NT-4040_01.07.0000.0015_1120, uses default credentials

> Remote attackers can gain privileged access to Nuuo NT-4040 Titan devices using known default credentials.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 13 Jul 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-jpq3-phrf-mc9q

## What is CVE-2016-6553?

CVE-2016-6553 is a critical vulnerability in Nuuo NT-4040 Titan, published on 13 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nuuo NT-4040 Titan, firmware NT-4040_01.07.0000.0015_1120, uses non-random default credentials of: admin:admin and localdisplay:111111. A remote network attacker can gain privileged access to a vulnerable device.

Weakness: CWE-255

## Which versions are affected by CVE-2016-6553?

It affects 1 product.


Products: Nuuo Nt-4040 Titan Firmware.

## How do I fix CVE-2016-6553?

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

## Is CVE-2016-6553 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-6553 and fix it if it is affected.

What it is: CVE-2016-6553 is a critical vulnerability in Nuuo NT-4040 Titan, published on 13 Jul 2018. 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-2016-6553 in the wild and no public exploit code.

Affected product: Nuuo NT-4040 Titan. 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-2016-6553/ (Markdown: https://insights.sbomify.com/CVE-2016-6553/index.md)
```

## Sources

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

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