# CVE-2016-5666: Auth bypass in n/a

> Remote attackers can bypass authentication on Crestron DM-TXRX-100-STR devices by manipulating client-side authentication flags.

- **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:** 3 Aug 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p5rj-hmpq-gmgh

## What is CVE-2016-5666?

CVE-2016-5666 is a critical authentication bypass vulnerability in n/a, published on 3 Aug 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Crestron Electronics DM-TXRX-100-STR devices with firmware before 1.3039.00040 rely on the client to perform authentication, which allows remote attackers to obtain access by setting the value of objresp.authenabled to 1.

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

It affects 1 product.


Products: Crestron Dm-Txrx-100-Str Firmware.

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

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

## Is CVE-2016-5666 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-5667](https://insights.sbomify.com/CVE-2016-5667/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-5668](https://insights.sbomify.com/CVE-2016-5668/): Auth bypass in n/a (critical 9.8)
- [CVE-2016-5669](https://insights.sbomify.com/CVE-2016-5669/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2016-5670](https://insights.sbomify.com/CVE-2016-5670/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2016-5671](https://insights.sbomify.com/CVE-2016-5671/): Cross-site request forgery in n/a (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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