dbcve.org
Stanza FirmwareOperating system · Lutron

CVE-2018-11682

CRITICAL · 9.8 CVSS v3.1 Published 2018-06-02
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
Default and unremovable support credentials allow attackers to gain total super user control of an IoT device through a TELNET session to products using the Stanza Lutron integration protocol Revision M to Revision Y. NOTE: The vendor disputes this id as not being a vulnerability because what can be done through the ports revolve around controlling lighting, not code execution. A certain set of commands are listed, which bear some similarity to code, but they are not arbitrary and do not allow admin-level control of a machine

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 · moderate confidence

Default and unremovable support credentials allow attackers to gain total super user control of IoT devices through TELNET sessions on products implementing the Stanza Lutron integration protocol from Revision M through Revision Y. The credentials are hardcoded and cannot be changed or removed, providing persistent access.

MitigationRestrict TELNET access via network segmentation/firewall rules, disable TELNET if possible, and contact Lutron for firmware updates that address the hardcoded credentials. Consider network monitoring for TELNET traffic to affected devices.

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
Stanza FirmwareOperating system
Affected:all versions
Radiora 2 FirmwareOperating system
Affected:all versions
Homeworks Qs FirmwareOperating system
Affected:all versions

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.1/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. Identify Lutron devices on your network
    Scan your network for devices with manufacturer OUI matching Lutron or devices advertising Lutron-specific service banners. Use network scanning tools (nmap, Angry IP Scanner) or check your network device inventory/MAC address tables for Lutron MAC prefixes.
    Affected if Any Lutron Stanza, Radiora 2, or Homeworks Qs devices are found on the network
  2. Check if TELNET service is listening on Lutron devices
    Run 'nmap -p 23 <target_ip>' or 'telnet <target_ip>' against identified Lutron device IPs to test if port 23 is open and responsive.
    Affected if Port 23/TELNET is open and accepts connections on any Lutron device
  3. Verify device firmware is a Lutron Stanza, Radiora 2, or Homeworks Qs version
    Connect to the device via available management interface or check device documentation/labels. The affected products are: Lutron Stanza, Lutron Radiora 2, and Lutron Homeworks Qs.
    Affected if The device is confirmed to be a Lutron Stanza, Radiora 2, or Homeworks Qs system
  4. Confirm TELNET provides superuser access without unique credentials
    Attempt TELNET login to the device using default support credentials (research Lutron documentation or test common default credential patterns for Lutron devices).
    Affected if TELNET login grants root/superuser access with default or hardcoded credentials that cannot be changed

You are affected if you have any Lutron Stanza, Radiora 2, or Homeworks Qs devices with TELNET port 23 accessible on your network, since all firmware versions contain the unremovable hardcoded credentials.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict TELNET access via network segmentation/firewall rules, disable TELNET if possible, and contact Lutron for firmware updates that address the hardcoded credentials. Consider network monitoring for TELNET traffic to affected devices.

Fix this in Stanza Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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