CVE-2018-15479
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. Devices did not authenticate themselves to the cloud in device to cloud communication. This lack of device authentication allowed an attacker to impersonate any device by guessing or learning their MAC address.
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, buttons, LED strips) fail to authenticate themselves when sending data to the cloud. An attacker can spoof device identity by guessing or obtaining the device MAC address, allowing unauthorized control or data injection.
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
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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 modelCheck the device label, packaging, or myStrom app to determine the exact model (Wifi Switch, Wifi Switch V2, Wifi Switch EU, Wifi Button, Wifi Button Plus, Wifi Bulb, or Wifi Led Strip)Affected if The device is any of these myStrom models
-
Locate the device in your networkFind the device IP address through your router's device list or the myStrom appAffected if Device is connected to your network
-
Access the device web interfaceOpen a browser and navigate to the device's IP address to view its status page, or open the myStrom app and select the device to view its detailsAffected if Device has a web interface or is paired with the app
-
Find the installed firmware versionOn the device web interface status page or in the myStrom app device details, locate the firmware version number displayedAffected if Firmware version is visible
-
Compare firmware version against affected rangesCheck if your firmware version falls below: Switch V1 < 2.66; Switch V2/EU/LED Strip < 3.80; Bulb < 2.58; Button/Button Plus < 2.73Affected if The installed firmware version is lower than the thresholds listed for your specific device model
You are affected if your myStrom device firmware version is lower than 2.66 (Switch V1), 3.80 (Switch V2/EU/LED Strip), 2.58 (Bulb), or 2.73 (Button/Button Plus).
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 all affected myStrom devices to the patched firmware versions (WiFi Switch V1 to 2.66, V2/EU/LED Strip to 3.80, Bulb to 2.58, Button/Button Plus to 2.73) which implement proper device-to-cloud authentication.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-15479 — 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-15479 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