Also, CVE-2020-8101 – Command execution due to unsanitized input
Do-it-yourself home security solutions are centerpieces of the modern lifestyle. From sensors to surveillance and anything in between, these solutions have our back while we’re at home and, even more importantly,
while we’re away.
Easily accessible from any part of the world, these live feeds offer peace of mind, letting you know that everything is fine back home. Securing this universe involves close collaboration between vendors, users and external security research teams.
Gaps in this fragile ecosystem can have unforeseen consequences and might even turn devices that protect our privacy into tools that violate it.
This research article aims to shed light on the security of the world’s best-sellers in the IoT space.
While looking into the LifeShield camera, Bitdefender researchers discovered several security issues that would allow a local attacker to:
These attacks are particularly effective in multi-tenant environments, such as small shops or shared homes that would allow a person connected to the same Wi-Fi to eavesdrop on conversations in the range of the vulnerable product.
Home users should keep a close eye on IoT devices and isolate them as much as possible from the local or guest network. This can be done by setting up a dedicated SSID exclusively for IoT devices.
Additionally, IoT users can use the free Bitdefender Smart Home Scanner app to scan for connected devices, identify and highlight vulnerable ones. IoT device owners should also make sure that they check for newer firmware and update devices as soon as the vendor releases new versions.
To minimize risks of compromise, smart home users should consider the adoption of a network cybersecurity solution integrated into the router, such as the NETGEAR Orbi or Nighthawk routers powered by Bitdefender Armor.
ADT, who now owns the LifeShield brand, was quick to address the issues once contact was established. Patches were applied to the production servers and all 1500 affected devices within 2 weeks of being notified
of the vulnerabilities.