dbcve.org
Dm Txrx 100 Str FirmwareOperating system · Crestron

CVE-2016-5666

CRITICAL · 9.8 CVSS v3.0 Published 2016-08-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
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.

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

The Crestron DM-TXRX-100-STR device with firmware before 1.3039.00040 suffers from a critical authentication bypass vulnerability. The device incorrectly delegates authentication validation to the client side rather than enforcing it server-side, allowing remote attackers to bypass authentication entirely by setting the objresp.authenabled parameter to 1.

MitigationUpgrade the device firmware to version 1.3039.00040 or later, which implements proper server-side authentication enforcement. If immediate patching is not possible, network segmentation and access controls should be applied to limit exposure to untrusted networks.

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
Dm Txrx 100 Str FirmwareOperating system
Affected:= 1.2866.00026

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.0/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 the device model
    Access the device web interface or check the device label/metadata to confirm it is a Crestron DM-TXRX-100-STR device
    Affected if The device is not a Crestron DM-TXRX-100-STR, as this vulnerability only affects that specific model
  2. Check the installed firmware version
    Log into the device administrative interface and navigate to the firmware/version information section, or use the device's API/CLI to query the firmware version
    Affected if The firmware version is lower than 1.3039.00040 (versions before 1.3039.00040 are affected, including 1.2866.00026)
  3. Verify device network exposure
    Review network configuration to determine if the device management interface is accessible from untrusted networks or the public internet
    Affected if The device is directly exposed to untrusted networks without firewall or access control protections
  4. Inspect authentication behavior
    Submit a request to the device with the parameter objresp.authenabled=1 in the request and observe whether authentication is bypassed or if the server enforces proper authentication
    Affected if The device allows authentication to be bypassed by client-side parameters, indicating the vulnerable authentication implementation is present

The environment is affected if the device is a Crestron DM-TXRX-100-STR running firmware version lower than 1.3039.00040 and is accessible to potential attackers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade the device firmware to version 1.3039.00040 or later, which implements proper server-side authentication enforcement. If immediate patching is not possible, network segmentation and access controls should be applied to limit exposure to untrusted networks.

Recommended fix High confidence

Firmware version 1.3039.00040 or later

  1. Identify the current firmware version of the DM-TXRX-100-STR device by accessing the web interface or administrative console
  2. Navigate to the official Crestron Electronics support website or authorized distribution channel
  3. Download firmware version 1.3039.00040 or later (the fixed release)
  4. Access the device administration interface and locate the firmware update section
  5. Upload the downloaded firmware file and initiate the update process
  6. Wait for the update to complete and the device to reboot
  7. Verify the new firmware version is installed and confirm the device is functioning normally
  8. Ensure that authentication is properly configured on the device post-update
Caveat Review release notes for any configuration or feature changes that may require adjustment during or after the firmware upgrade

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

Fix this in Dm Txrx 100 Str Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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