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 process of registering a device with a cloud account was based on an activation code derived from the device MAC address. By guessing valid MAC addresses or using MAC addresses printed on devices in shops and reverse engineering the protocol, an attacker would have been able to register previously unregistered devices to their account. When the rightful owner would have connected them after purchase to their WiFi network, the devices would not have registered with their account, would subsequently not have been controllable from the owner's mobile app, and would not have been visible in the owner's account. Instead, they would have been under control of the attacker.

Project Subscriptions

Vendors Products
Mystrom Subscribe
Wifi Bulb Subscribe
Wifi Bulb Firmware Subscribe
Wifi Button Subscribe
Wifi Button Firmware Subscribe
Wifi Button Plus Subscribe
Wifi Button Plus Firmware Subscribe
Wifi Led Strip Subscribe
Wifi Led Strip Firmware Subscribe
Wifi Switch Subscribe
Wifi Switch Eu Subscribe
Wifi Switch Eu Firmware Subscribe
Wifi Switch Firmware Subscribe
Advisories
Source ID Title
EUVD EUVD EUVD-2018-7356 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 process of registering a device with a cloud account was based on an activation code derived from the device MAC address. By guessing valid MAC addresses or using MAC addresses printed on devices in shops and reverse engineering the protocol, an attacker would have been able to register previously unregistered devices to their account. When the rightful owner would have connected them after purchase to their WiFi network, the devices would not have registered with their account, would subsequently not have been controllable from the owner's mobile app, and would not have been visible in the owner's account. Instead, they would have been under control of the attacker.
Fixes

Solution

No solution given by the vendor.


Workaround

No workaround given by the vendor.

History

No history.

Projects

Sign in to view the affected projects.

cve-icon MITRE

Status: PUBLISHED

Assigner: mitre

Published:

Updated: 2024-08-05T09:54:03.428Z

Reserved: 2018-08-17T00:00:00.000Z

Link: CVE-2018-15478

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Modified

Published: 2018-08-30T17:29:01.363

Modified: 2024-11-21T03:50:53.880

Link: CVE-2018-15478

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

No data.

Weaknesses