dbcve.org
Tsw X60 FirmwareOperating system · Crestron

CVE-2018-10630

CRITICAL · 9.8 CVSS v3.0 Published 2018-08-10
Fix available
A fix is available. Upgrade to 1.502.0047.001 / 2.001.0037.001 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
For Crestron TSW-X60 version prior to 2.001.0037.001 and MC3 version prior to 1.502.0047.001, The devices are shipped with authentication disabled, and there is no indication to users that they need to take steps to enable it. When compromised, the access to the CTP console is left open.

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
How this class of weakness works · CWE-284

The application fails to correctly restrict what a user can do or reach, so functions or resources are available to people who should not have them. Attackers simply probe for the paths where the check is missing or wrong. The fix is to enforce access-control decisions consistently on every request, evaluated against the acting user rather than assumed from context.

General guidance for the improper access control class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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
Tsw X60 FirmwareOperating system
Affected:< 2.001.0037.001
Mc3 FirmwareOperating system
Affected:< 1.502.0047.001

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

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
Upgrade available Upgrade to 1.502.0047.001 / 2.001.0037.001 or later
Fixed in 1.502.0047.0012.001.0037.001
Vendor patch ics-cert.us-cert.gov →
Recommended fix High confidence

TSW X60: 2.001.0037.001 | MC3: 1.502.0047.001

  1. Obtain the firmware upgrade package for your device model from Crestron's official support channels
  2. For TSW-X60: Upgrade firmware to version 2.001.0037.001 or later
  3. For MC3: Upgrade firmware to version 1.502.0047.001 or later
  4. After upgrading, access the CTP console configuration
  5. Enable authentication in the CTP console settings
  6. Verify that authentication is now required for console access
  7. If present, change any default credentials to strong, unique passwords

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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