CVE-2018-13341
A public proof of concept exists; no exploitation attested.
- Published2018-08-10
- Fixed in1.502.0047.00
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Crestron TSW-X60 all versions prior to 2.001.0037.001 and MC3 all versions prior to 1.502.0047.00, The passwords for special sudo accounts may be calculated using information accessible to those with regular user privileges. Attackers could decipher these passwords, which may allow them to execute hidden API calls and escape the CTP console sandbox environment with elevated privileges.
Timeline
dates in UTC- 2018-08-1019:29CVE publishedNVD
- 2026-10-2319:23First public proof of conceptPoC-in-GitHub
Observed activity
isMalicious corpus · updated 2026-10-23 18:48 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2018-13341?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2018-13341?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.502 | < 1.502.0047.00 | 1.502.0047.00 | NVD |
| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 2.1 | < 2.001.0037.001 | 2.001.0037.001 | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Crestron TSW-X60 and MC3
TSW-X60: all versions prior to 2.001.0037.001; · MC3: all versions prior to 1.502.0047.001
Fix
- Update Crestron mc3 firmware to 1.502.0047.00
- Vendor fix CISA ICSA-18-221-01 · 2 productsMC3 (login required) - https://www.crestron.com/en-US/Software-Firmware/Firmware/3-Series-Processors/MC3/1-502-0047-001
- Mitigation from the vendor CISA ICSA-18-221-01 · 2 productsTSW-X60 (login required) - https://www.crestron.com/en-US/Software-Firmware/Firmware/Touchpanels/TSW-560-TSW-760-TSW-1060/2-001-0040-01
- Mitigation from the vendor CISA ICSA-18-221-01 · 2 productsCrestron also recommends users refer to Crestron's Online Help for more information about these and other vulnerabilities (Article #5471). Information for hardening devices is available in Article #5571.
Advisories and patches
- ics-cert.us-cert.govMitigation
Detection
read 2026-10-23 19:23 UTC- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- 2 repositories, unverifiedaxcheron/crestron_getsudopwdRajChowdhury240/CVE-2018-13341 PoC-in-GitHub
Sources
- NVDCVSS 3.08.8read 2026-10-23
- NVDCVSS 2.04read 2026-10-23
- FIRST EPSSEPSS score3.7 %2026-10-22
- PoC-in-GitHubproof of concept2read 2026-10-23
Technical details
- CVSS v3 Vector
- CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Published
- 2018-08-10
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2018-13341?
Is CVE-2018-13341 actively exploited?
What is the CVSS score for CVE-2018-13341?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.