dbcve.org
Wifi Switch FirmwareOperating system · Mystrom

CVE-2018-15480

HIGH · 8.8 CVSS v3.0 Published 2018-08-30
Fix available
A fix is available. Upgrade to 2.58 / 2.66 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
An 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 cloud API had a hidden parameter, which allowed an authenticated user to reconfigure the server URL for a device registered to their account. In combination with an insecure device registration vulnerability, this allowed an attacker to reconfigure a maliciously registered device to their own rogue replica of the myStrom API and issue commands to the device, including firmware update commands.

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

The myStrom cloud API contains a hidden parameter allowing authenticated users to reconfigure the server URL for devices registered to their account. When combined with an insecure device registration vulnerability, attackers can register a malicious device and redirect it to a rogue API server, enabling command injection including firmware updates.

MitigationUpdate firmware to the fixed versions (V1>=2.66, V2/EU/LED Strip>=3.80, Bulb>=2.58, Button/Button Plus>=2.73) and remediate the insecure device registration in the cloud API.

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
Wifi Switch FirmwareOperating system
Affected:< 2.66< 3.80
Wifi Button Plus FirmwareOperating system
Affected:< 2.73
Wifi Button FirmwareOperating system
Affected:< 2.73
Wifi Switch Eu FirmwareOperating system
Affected:< 3.80
Wifi Bulb FirmwareOperating system
Affected:< 2.58
Wifi Led Strip FirmwareOperating system
Affected:< 3.80

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/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 myStrom device models in your environment
    Inventory all myStrom devices (Wifi Switch, Wifi Button, Wifi Button Plus, Wifi Switch EU, Wifi Bulb, Wifi LED Strip) by reviewing your myStrom cloud account, network DHCP leases, or physical device labels
    Affected if Any of these device models are present in the environment
  2. Retrieve firmware version from each device
    Use the myStrom mobile app to check device details, or query the device directly via its local API at http://<device-ip>/api/info to obtain the firmware version field
    Affected if Firmware version is below 2.66 for Wifi Switch, below 3.80 for Wifi Switch EU or LED Strip, below 2.73 for Button/Button Plus, or below 2.58 for Bulb
  3. Inspect cloud API device configuration
    Log into the myStrom cloud management portal and review each device's registered server URL configuration. Look for any unexpected or user-modifiable server endpoint fields in the device settings API responses
    Affected if The API exposes a parameter that allows modification of the device server URL for devices registered to your account
  4. Verify device registration security
    Examine the device registration process in the cloud API by reviewing API request/response traffic when adding a new device. Check if the registration mechanism validates ownership or allows arbitrary device hijacking
    Affected if The device registration endpoint does not properly validate that the registering user owns the device serial number, allowing unauthorized device registration
  5. Check for rogue API server assignments
    Query each device's current server configuration via the local API endpoint /api/info or through the cloud API, and verify all server URLs point to the official myStrom cloud endpoints (*.mystrom.ch or *.mystrom.com)
    Affected if Any device is configured to connect to a server URL other than the official myStrom cloud infrastructure

A user is affected if any myStrom device runs firmware below the fixed versions AND the cloud API allows modification of device server URLs without proper ownership validation.

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
Upgrade available Upgrade to 2.58 / 2.66 / 2.73 or later
Fixed in 2.582.662.73
Interim mitigation

Update firmware to the fixed versions (V1>=2.66, V2/EU/LED Strip>=3.80, Bulb>=2.58, Button/Button Plus>=2.73) and remediate the insecure device registration in the cloud API.

Fix this in Wifi Switch Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing16.0 h
  • Review / QA8.0 h
56.0 hours of engineering $9,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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