dbcve.org
Dm Txrx 100 Str FirmwareOperating system · Crestron

CVE-2016-5670

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 have a hardcoded password of admin for the admin account, which makes it easier for remote attackers to obtain access via the web management interface.

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

Crestron Electronics DM-TXRX-100-STR devices running firmware versions prior to 1.3039.00040 contain a hardcoded password of 'admin' for the admin account. This hardcoded credential allows remote attackers to authenticate to the web management interface and gain full administrative control of the device.

MitigationUpdate firmware to version 1.3039.00040 or later to replace the hardcoded credential with a unique, secure password. If immediate patching is not possible, restrict network access to the web management interface via firewall rules or VPN.

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. Confirm device model
    Identify if the device is a Crestron DM-TXRX-100-STR by checking the device label, web interface header, or SNMP sysDescr value
    Affected if Device is not a DM-TXRX-100-STR model
  2. Check installed firmware version
    Access the device web management interface and navigate to the status or system information page to view the firmware version, or use SNMP to query the firmware version OID
    Affected if Firmware version is 1.2866.00026 or any version prior to 1.3039.00040
  3. Verify admin account password
    Attempt to log into the web management interface using the username 'admin' with password 'admin', or examine configuration backup files if available
    Affected if Login succeeds with admin/admin credentials
  4. Check web interface accessibility
    Determine if the device web management interface is reachable from network segments outside the trusted management network
    Affected if Web interface is exposed to untrusted networks without firewall filtering

A user is affected if they have a DM-TXRX-100-STR device running firmware version 1.2866.00040 or earlier, where the default admin account can be accessed with the hardcoded password 'admin'.

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

Update firmware to version 1.3039.00040 or later to replace the hardcoded credential with a unique, secure password. If immediate patching is not possible, restrict network access to the web management interface via firewall rules or VPN.

Recommended fix High confidence

Firmware version 1.3039.00040 or later

  1. Identify the current firmware version of the Crestron DM-TXRX-100-STR device via the web management interface or console
  2. Download firmware version 1.3039.00040 or later from the official Crestron Electronics support website
  3. Review the firmware upgrade instructions in the Crestron DM-TXRX-100-STR installation guide
  4. Back up the current device configuration if possible
  5. Upload and apply the firmware upgrade through the device's web management interface or maintenance tool
  6. After upgrading, verify the new firmware version is installed
  7. Change the default admin password immediately after upgrade to a strong, unique password
  8. Verify the web management interface is accessible only through trusted networks or VPNs
Caveat Firmware upgrades may temporarily interrupt device operation; test in non-production environment first

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
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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