CVE-2018-11229
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 command injection 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 confidenceUnauthenticated command injection in the Crestron Toolbox Protocol (CTP) allows remote attackers to execute arbitrary operating system commands on affected Crestron touch panel devices (TSW-1060, TSW-760, TSW-560, and NC variants) by injecting malicious commands into CTP requests, leading to complete device compromise without any authentication credentials.
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 your device modelLocate the model number on the device label or check the device inventory documentation. Confirm it is one of: TSW-1060, TSW-760, TSW-560, or an NC-series variant.Affected if The device is NOT one of these models, then this CVE does not apply to your device.
-
Check the Crestron Toolbox Protocol firmware versionAccess the device admin interface or use Crestron Toolbox software to retrieve the firmware version. Navigate to the system information or firmware update section.Affected if The installed firmware version is lower than 2.001.0037.001, the device is running a vulnerable version.
-
Determine if CTP service is enabledCheck the device network configuration or service status to see if the Crestron Toolbox Protocol (CTP) service is active and listening on the network.Affected if CTP is disabled or not configured, the command injection attack surface may not be exposed, but the device remains vulnerable if CTP is later enabled.
-
Assess network exposure of CTP portsReview firewall rules and network segmentation to determine if CTP ports (typically port 41795 for CTP) are accessible from untrusted network segments or the internet.Affected if CTP ports are exposed to untrusted networks without network segmentation, the device is at higher risk of remote exploitation.
You are affected if your device is a TSW-1060, TSW-760, TSW-560, or NC variant AND the firmware version is below 2.001.0037.001, regardless of CTP accessibility.
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
Upgrade affected Crestron TSW touch panel devices to firmware version 2.001.0037.001 or later to remediate the command injection vulnerability. If patching is not immediately possible, restrict network access to CTP ports and isolate affected devices from untrusted networks.
2.001.0037.001
- 1. Obtain the fixed firmware version 2.001.0037.001 from the official Crestron support portal (support.crestron.com)
- 2. Review the Crestron firmware upgrade documentation for your specific device model (TSW-1060, TSW-760, TSW-560, TSW-1060-NC, TSW-760-NC, or TSW-560-NC)
- 3. Backup current device configuration if applicable
- 4. Upload the firmware file 2.001.0037.001 to the device using the Crestron Toolbox software or device web interface
- 5. Verify the firmware upgrade was successful by checking the device firmware version
- 6. Confirm the Crestron Toolbox Protocol service is functioning normally after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-11229 — 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-11229 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