dbcve.org
Dm Txrx 100 Str FirmwareOperating system · Crestron

CVE-2016-5669

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 use a hardcoded 0xb9eed4d955a59eb3 X.509 certificate from an OpenSSL Test Certification Authority, which makes it easier for remote attackers to conduct man-in-the-middle attacks against HTTPS sessions by leveraging the certificate's trust relationship.

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 DM-TXRX-100-STR devices ship with a hardcoded X.509 certificate from an OpenSSL Test Certification Authority embedded in firmware versions prior to 1.3039.00040. Since test certificates and their private keys are publicly known, remote attackers possessing this known key can perform man-in-the-middle attacks against HTTPS sessions, decrypting and intercepting sensitive traffic.

MitigationUpdate affected devices to firmware version 1.3039.00040 or later, which replaces the hardcoded test certificate with a unique, properly generated certificate. If firmware updates are unavailable, avoid transmitting sensitive data over HTTPS on these devices until remediation is possible.

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 is DM-TXRX-100-STR
    Access the device web interface or check the physical device label to verify the exact model number matches DM-TXRX-100-STR
    Affected if Device is a DM-TXRX-100-STR unit
  2. Check installed firmware version
    Log into the device admin interface and navigate to the firmware or system information page to view the current firmware version number
    Affected if Firmware version is below 1.3039.00040 (for example, 1.2866.00026)
  3. Verify HTTPS is enabled on the device
    Check the device network settings or security configuration to determine if HTTPS/TLS connections are enabled for management or streaming
    Affected if HTTPS is enabled and the device uses the default hardcoded certificate for TLS connections

The device is affected if it is a Crestron DM-TXRX-100-STR running firmware version prior to 1.3039.00040 with HTTPS enabled.

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 affected devices to firmware version 1.3039.00040 or later, which replaces the hardcoded test certificate with a unique, properly generated certificate. If firmware updates are unavailable, avoid transmitting sensitive data over HTTPS on these devices until remediation is possible.

Recommended fix High confidence

firmware 1.3039.00040 or later

  1. 1. Identify the current firmware version of the DM-TXRX-100-STR device through the web interface or administrative console.
  2. 2. Navigate to the firmware update or maintenance section of the device management interface.
  3. 3. Obtain the firmware version 1.3039.00040 or later from the official Crestron Electronics support website.
  4. 4. Upload and apply the new firmware to the device following the manufacturer's documented upgrade procedure.
  5. 5. After the firmware update completes, verify the device is operational and confirm the new firmware version is installed.
  6. 6. Since this vulnerability involves a hardcoded certificate, consider regenerating any SSL/TLS certificates used by the device after the upgrade to ensure unique, properly trusted certificates are in place.
Caveat Review Crestron release notes for any configuration or feature changes between versions; firmware updates may require brief device downtime

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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