CVE-2018-15476
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 · uneditedAn issue was discovered in myStrom WiFi Switch V1 before 2.66, WiFi Switch V2 before 3.80, WiFi Switch EU before 3.80, WiFi Bulb before 2.58, WiFi LED Strip before 3.80, WiFi Button before 2.73, and WiFi Button Plus before 2.73. The SSL/TLS server certificate in the device to cloud communication was not verified by the device. As a result, an attacker in control of the network traffic of a device could have taken control of a device by intercepting and modifying commands issued from the server to the device in a Man-in-the-Middle attack. This included the ability to inject firmware update commands into the communication and cause the device to install maliciously modified firmware.
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 confidencemyStrom WiFi devices (switches, bulbs, LED strips, buttons) fail to verify SSL/TLS certificates when communicating with cloud servers. This allows Man-in-the-Middle attackers to intercept and modify traffic, including injecting malicious firmware update commands that devices will accept and execute.
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.66< 3.80< 2.73< 2.73< 3.80< 2.58< 3.80CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/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 myStrom device modelLocate the physical device or check your myStrom app to determine if it is a Wifi Switch, Wifi Switch EU, Wifi Button, Wifi Button Plus, Wifi Bulb, or Wifi LED Strip. Each model has different patched version requirements.Affected if Device model is any of: Wifi Switch, Wifi Button Plus, Wifi Button, Wifi Switch EU, Wifi Bulb, or Wifi LED Strip and firmware version is unknown or below patched levels
-
Check firmware version via web interfaceAccess the device's web interface by entering its IP address in a browser. Navigate to the settings or status page to locate the firmware version information. If the device has no web interface, use the myStrom mobile app to check the firmware version under device details.Affected if Firmware version cannot be determined or is below 2.66 for Wifi Switch V1, below 3.80 for Wifi Switch V2/EU/LED Strip, below 2.73 for Button/Button Plus, or below 2.58 for Bulb
-
Compare version against affected rangesCross-reference your detected firmware version with the affected ranges: Wifi Switch < 2.66 or < 3.80 depending on hardware version; Wifi Switch EU < 3.80; Wifi Button/Button Plus < 2.73; Wifi Bulb < 2.58; Wifi LED Strip < 3.80. Note that Wifi Switch has two version thresholds based on hardware generation.Affected if Installed firmware version falls within any of these ranges: Switch V1 < 2.66, Switch V2/EU/LED Strip < 3.80, Button/Button Plus < 2.73, Bulb < 2.58
You are affected if you have any myStrom WiFi device running firmware below the patched version for its specific model (2.66+, 2.73+, 2.58+, or 3.80+ depending on device type).
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.
From vendor data2.582.662.73
Update affected myStrom devices to the patched firmware versions (V1: 2.66+, V2/EU/LED Strip: 3.80+, Bulb: 2.58+, Button/Button Plus: 2.73+). Until patched, isolate devices on restricted network segments to reduce MITM attack surface.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15476 — 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-15476 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