CVE-2018-11228
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 · uneditedCrestron TSW-1060, TSW-760, TSW-560, TSW-1060-NC, TSW-760-NC, and TSW-560-NC devices before 2.001.0037.001 allow unauthenticated remote code execution via a Bash shell service in Crestron Toolbox Protocol (CTP).
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 confidenceCrestron TSW series touch panel devices (TSW-1060, TSW-760, TSW-560, and NC variants) contain an unauthenticated remote code execution vulnerability in the Bash shell service implementation of the Crestron Toolbox Protocol (CTP). An attacker can send specially crafted CTP packets to execute arbitrary shell commands without any authentication, achieving full device compromise.
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< 2.001.0037.001CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Crestron TSW series devices on the networkInventory network devices and locate any Crestron TSW-1060, TSW-760, TSW-560, or NC model touch panels. These can often be discovered via network scanning or by reviewing device DHCP leases and MAC vendor prefixes (Crestron OUI).Affected if Any Crestron TSW series touch panel (TSW-1060, TSW-760, TSW-560, or NC variants) exists on the network.
-
Determine Crestron Toolbox Protocol firmware versionAccess the device web interface or use Crestron Toolbox software to retrieve the firmware version. The version is displayed in the device info or system status page. Compare the installed version against the affected range: versions prior to 2.001.0037.001 are vulnerable.Affected if The device runs Crestron Toolbox Protocol firmware version lower than 2.001.0037.001.
-
Verify CTP Bash shell service is enabledCheck the device configuration via the web interface or Toolbox software for the Crestron Toolbox Protocol (CTP) service settings. Confirm whether the Bash shell service feature within CTP is enabled. This is typically found under protocol settings or shell access configuration.Affected if The Bash shell service component of Crestron Toolbox Protocol is enabled on the device.
-
Assess network exposure of CTP serviceScan the network for open ports associated with Crestron Toolbox Protocol (typically port 5017 or as configured). Determine if these ports are accessible from untrusted network segments or the internet by reviewing firewall rules and network ACLs.Affected if The CTP port is exposed to untrusted networks or accessible without network segmentation.
You are affected if you have any Crestron TSW series devices (TSW-1060, TSW-760, TSW-560, or NC) running Crestron Toolbox Protocol firmware versions earlier than 2.001.0037.001 with the Bash shell service enabled and the CTP port exposed to untrusted networks.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2.001.0037.001
Apply vendor firmware version 2.001.0037.001 or later to all affected devices. If immediate patching is not feasible, isolate affected devices on a restricted network segment and block CTP port access from untrusted networks.
2.001.0037.001
- 1. Identify all affected Crestron device models (TSW-1060, TSW-760, TSW-560, TSW-1060-NC, TSW-760-NC, TSW-560-NC) in your environment
- 2. Check the current firmware version on each device via the Crestron Toolbox or device web interface
- 3. Download the firmware version 2.001.0037.001 or later from the official Crestron support portal (support.crestron.com)
- 4. Upload the new firmware to each affected device using the Crestron Toolbox software
- 5. Verify the firmware upgrade was successful by confirming the new version number
- 6. Verify the vulnerability is no longer present by confirming the Bash shell service is no longer exposed via Crestron Toolbox Protocol
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11228 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-11228 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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