{"id":47866,"date":"2023-04-14T07:49:47","date_gmt":"2023-04-14T11:49:47","guid":{"rendered":"https:\/\/www.kaspersky.com\/blog\/?p=47866"},"modified":"2023-05-12T07:36:46","modified_gmt":"2023-05-12T11:36:46","slug":"3-reasons-not-to-use-smart-locks","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com\/blog\/3-reasons-not-to-use-smart-locks\/47866\/","title":{"rendered":"Three reasons not to use smart locks"},"content":{"rendered":"<p>Smart locks can be really handy. There are plenty of them on the market and lots of different types to choose from. Some are able to detect when the owner (or, rather \u2014 their smartphone) is approaching, and open without a key. Others are controlled remotely, allowing you to open the door to friends or relatives without being home. Still others also provide video surveillance: someone rings the doorbell, and you immediately see on your smartphone who it is.<\/p>\n<p>However, smart devices carry risks that users of traditional, offline locks never have to worry about. A careful study of these risks reveals a full three reasons to stick to the old way. Let\u2019s take a look at them\u2026<\/p>\n<h2>First reason: smart locks are physically more vulnerable than normal locks<\/h2>\n<p>The problem here is that smart locks combine two different concepts. In theory, these locks should have a reliable smart component, while at the same time provide robust protection against physical tampering so they can\u2019t be opened with, say, a screwdriver or penknife. Combining these two concepts doesn\u2019t always work: the result is usually either a flimsy smart lock, or a heavy-duty iron lock with vulnerable software.<\/p>\n<p>We\u2019ve already talked about some particularly egregious examples of locks incapable of doing their jobs in another <a href=\"https:\/\/www.kaspersky.com\/blog\/why-smart-padlocks-suck\/26880\/\" target=\"_blank\" rel=\"noopener nofollow\">post<\/a>. They include a cool padlock with a fingerprint scanner \u2014 under which there happens to be an opening mechanism potentially accessible to anyone (a lever). Plus a smart lock for bicycles \u2014 which can be taken apart with a screwdriver.<\/p>\n<div id=\"attachment_47869\" style=\"width: 1093px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2023\/04\/13101349\/3-reasons-not-to-use-smart-locks-1.jpg\"><img decoding=\"async\" aria-describedby=\"caption-attachment-47869\" class=\"size-full wp-image-47869\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2023\/04\/13101349\/3-reasons-not-to-use-smart-locks-1.jpg\" alt=\"Example of a physically vulnerable smart lock\" width=\"1083\" height=\"633\"><\/a><p id=\"caption-attachment-47869\" class=\"wp-caption-text\">The top panel with the fingerprint scanner is easy to remove with a knife. The opening mechanism is accessible under the panel. <a href=\"https:\/\/www.youtube.com\/watch?v=uVvEkcN5tW8\" target=\"_blank\" rel=\"noopener nofollow\">Source<\/a>.<\/p><\/div>\n<h2>Second reason: issues with the \u201csmart\u201d component<\/h2>\n<p>Making the \u201csmart\u201d component secure enough is also not easy. It\u2019s important to remember that developers of such devices often prioritize functionality over protection. The most recent example is the Akuvox E11, a device designed not for the home use, but for offices. The Akuvox E11 is a smart intercom with a terminal for receiving a video stream from the built-in camera, plus a button to open the door. And, as it\u2019s a smart device, you can control it via the smartphone app.<\/p>\n<div id=\"attachment_47868\" style=\"width: 1205px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2023\/04\/13101334\/3-reasons-not-to-use-smart-locks-2.jpg\"><img decoding=\"async\" aria-describedby=\"caption-attachment-47868\" class=\"size-full wp-image-47868\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2023\/04\/13101334\/3-reasons-not-to-use-smart-locks-2.jpg\" alt=\"Akuvox E11 smart intercom\" width=\"1195\" height=\"381\"><\/a><p id=\"caption-attachment-47868\" class=\"wp-caption-text\">The Akuvox E11 lock has multiple vulnerabilities, allowing unauthorized access to the given premises without any problems. <a href=\"https:\/\/claroty.com\/team82\/research\/the-silent-spy-among-us-modern-attacks-against-smart-intercoms\" target=\"_blank\" rel=\"noopener nofollow\">Source<\/a>.<\/p><\/div>\n<p>The software has been <a href=\"https:\/\/claroty.com\/team82\/research\/the-silent-spy-among-us-modern-attacks-against-smart-intercoms\" target=\"_blank\" rel=\"nofollow noopener\">implemented<\/a> in such a way that anyone can gain access to both video and sound from the camera at any time. And if you\u2019ve not thought about isolating the web interface from the internet, anyone will be able to control the lock and open the door. This is a textbook example of insecure software development: video requests miss authorization checks; part of the web interface is accessible without a password; and the password itself is easy to crack due to encryption with a fixed key that\u2019s the same for all devices.<\/p>\n<p>Want more examples? Here you go\u2026 <a href=\"https:\/\/cyberriskleaders.com\/security-vulnerability-in-popular-smart-door-lock\/\" target=\"_blank\" rel=\"nofollow noopener\">This article<\/a> talks about a lock that allows nearby intruders to get your Wi-Fi network password. <a href=\"https:\/\/www.cnet.com\/home\/security\/smart-lock-has-a-security-vulnerability-that-leaves-homes-open-for-attacks\/\" target=\"_blank\" rel=\"nofollow noopener\">Here<\/a>, a smart lock protects data transfer poorly: an attacker can eavesdrop on the radio channel and seize control. And <a href=\"https:\/\/critical.lt\/blog\/we-lock-unlocking-smart-locks-with-web-vulnerabilities\/\" target=\"_blank\" rel=\"nofollow noopener\">here<\/a> is another example of a poorly secured web interface.<\/p>\n<h2>Third reason: the software needs to be updated regularly<\/h2>\n<p>A typical smartphone receives updates for two or three years after its release. As for low-budget IoT devices, support may be withheld even earlier. Updating a smart device via the internet is fairly straightforward. However, maintaining support for devices requires resources and money on the part of the vendor.<\/p>\n<p>This in itself can be a problem, such as when the vendor <a href=\"https:\/\/smartlockpicking.com\/tutorial\/my-smart-lock-vendor-disappeared\/\" target=\"_blank\" rel=\"nofollow noopener\">disables the cloud infrastructure<\/a> and the device stops working. But even if smart-lock functionality is preserved, vulnerabilities that were unknown to the vendor at the time of release could yet appear.<\/p>\n<p>For example, in 2022, researchers <a href=\"https:\/\/newsroom.nccgroup.com\/news\/ncc-group-uncovers-bluetooth-low-energy-ble-vulnerability-that-puts-millions-of-cars-mobile-devices-and-locking-systems-at-risk-447952\" target=\"_blank\" rel=\"nofollow noopener\">discovered<\/a> a vulnerability in the Bluetooth Low Energy protocol, which many companies have adopted as the standard for contactless authentication when unlocking various devices (including smart locks). This vulnerability opens the door (so to speak) to so-called relay attacks, which require the attacker to be close to the smart-lock owner and use special (but relatively inexpensive) equipment. Armed with this hardware, the attacker can relay signals between the victim\u2019s smartphone and the smart lock. This tricks the smart lock into thinking that the owner\u2019s smartphone is nearby (and not in a shopping mall three miles away), whereupon it unlocks the door.<\/p>\n<div id=\"attachment_47870\" style=\"width: 983px\" class=\"wp-caption aligncenter\"><a href=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2023\/04\/13101406\/3-reasons-not-to-use-smart-locks-3.jpg\"><img decoding=\"async\" aria-describedby=\"caption-attachment-47870\" class=\"size-full wp-image-47870\" src=\"https:\/\/media.kasperskydaily.com\/wp-content\/uploads\/sites\/92\/2023\/04\/13101406\/3-reasons-not-to-use-smart-locks-3.jpg\" alt=\"Example of a relay attack-vulnerable smart lock\" width=\"973\" height=\"973\"><\/a><p id=\"caption-attachment-47870\" class=\"wp-caption-text\">A Kwikset lock vulnerable to a relay attack using a bug in the Bluetooth Low Energy protocol. <a href=\"https:\/\/www.kwikset.com\/products\/detail\/kevo-traditional-touch-to-open-smart-lock-2nd-gen\" target=\"_blank\" rel=\"noopener nofollow\">Source<\/a>.<\/p><\/div>\n<p>Since smart-lock software is highly complex, the probability of its containing serious vulnerabilities is never zero. If one is discovered, the vendor should promptly release an update and send it to all sold devices. But what if the model was discontinued or is no longer supported?<\/p>\n<p>With smartphones, we solve this problem by buying a new device every two to three years. How often do you plan to replace a door lock connected to the internet? We generally expect such devices to last for decades, not a couple of years (until the vendor pulls support or goes bust).<\/p>\n<h2>So, what to do?<\/h2>\n<p>It should be understood that all locks (not only smart ones) can be cracked. However, when deciding to install a smart device instead of a standard lock, think carefully: do you really need to be able to open the door from your smartphone? If you answer yes to this question, at least consider the following points:<\/p>\n<ul>\n<li>Look for information about the particular device before purchasing.<\/li>\n<li>Read not only reviews about convenience and features of the smart lock, but also reports of potential problems and risks.<\/li>\n<li>Go for a newer device: chances are the vendor will maintain support for it a little longer.<\/li>\n<li>Once you\u2019ve bought a device, study its networking features and think carefully about whether you need them; it would make sense to disable any that could be dangerous.<\/li>\n<li>Don\u2019t forget to <a href=\"https:\/\/www.kaspersky.com\/premium?icid=gl_bb2023-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener nofollow\">protect<\/a> your computers, especially if they\u2019re on the same network as the smart lock. It would a double-shame if a malware infection on your computer were to also cause your home\u2019s doors to be flung open.<\/li>\n<\/ul>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"premium-generic\">\n","protected":false},"excerpt":{"rendered":"<p>Better put them on something not very valuable or necessary. Here we explain why.<\/p>\n","protected":false},"author":665,"featured_media":47867,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1789],"tags":[658,794,1373,659],"class_list":{"0":"post-47866","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-technology","8":"tag-internet-of-things","9":"tag-iot","10":"tag-locks","11":"tag-smart-devices"},"hreflang":[{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/3-reasons-not-to-use-smart-locks\/47866\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/3-reasons-not-to-use-smart-locks\/25504\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/3-reasons-not-to-use-smart-locks\/20937\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/3-reasons-not-to-use-smart-locks\/10555\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/3-reasons-not-to-use-smart-locks\/28120\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/3-reasons-not-to-use-smart-locks\/25811\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/3-reasons-not-to-use-smart-locks\/26227\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/3-reasons-not-to-use-smart-locks\/28716\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/3-reasons-not-to-use-smart-locks\/27713\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/3-reasons-not-to-use-smart-locks\/35048\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/3-reasons-not-to-use-smart-locks\/11431\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/3-reasons-not-to-use-smart-locks\/20473\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/3-reasons-not-to-use-smart-locks\/21143\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/3-reasons-not-to-use-smart-locks\/30046\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/3-reasons-not-to-use-smart-locks\/33692\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/3-reasons-not-to-use-smart-locks\/26133\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/3-reasons-not-to-use-smart-locks\/31816\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/3-reasons-not-to-use-smart-locks\/31503\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com\/blog\/tag\/iot\/","name":"IoT"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/47866","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/665"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=47866"}],"version-history":[{"count":3,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/47866\/revisions"}],"predecessor-version":[{"id":47872,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/47866\/revisions\/47872"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/47867"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=47866"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=47866"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=47866"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}