{"id":22897,"date":"2019-07-01T06:00:34","date_gmt":"2019-07-01T10:00:34","guid":{"rendered":"https:\/\/www.kaspersky.com.au\/blog\/hacking-things\/22897\/"},"modified":"2019-11-15T22:24:24","modified_gmt":"2019-11-15T11:24:24","slug":"hacking-things","status":"publish","type":"post","link":"https:\/\/www.kaspersky.com.au\/blog\/hacking-things\/22897\/","title":{"rendered":"Hacking our boss&#8217;s smart home"},"content":{"rendered":"<p>The idea of a smart home is becoming more and more mainstream nowadays. Previously appealing mostly to geeks and people who always buy the newest toys, smart home setups have become quite popular, and a basic setup can even be affordable.<\/p>\n<p>One of our colleagues joined the smart home party and added some fancy, techie things to his new home. After he installed everything, he thought researchers from <a href=\"https:\/\/ics-cert.kaspersky.com\/\" target=\"_blank\" rel=\"noopener noreferrer\">Kaspersky ICS CERT<\/a> might have some fun playing with his new toy. Of course, security researchers\u2019 idea of a good time is trying to break new toys. And, of course, they thought it was a marvelous idea. And, of course, they succeeded. And so, of course, here is the short story of how they hacked that smart home and what they were able to do with it once they were in.<\/p>\n<h2>Hacking begins<\/h2>\n<p>The setup is as follows: The house, in a remote location, has a Fibaro Home Center Lite smart hub, which is responsible for managing all of the smart things that are connected to it.<\/p>\n<p>The smart things in the home include lights with a motion sensor that can automatically power on and off; a fridge, a stereo system, and a sauna heater that can be remotely manipulated and also turned on and off. Several smoke detectors and flood sensors, as well as a couple of IP cameras for monitoring the house are also connected to the same hub. And, of course, the heating system and the entrance door with a smart video doorbell, are managed from the hub as well.<\/p>\n<p>All of that was connected to a home wireless network. What the security researchers knew was the model of smart home hub and its IP address.<\/p>\n<h3>How it works: Narrowing the attack surface<\/h3>\n<p>So, how do you attack a smart home? It usually goes as follows: The team of security researchers tries to jot down all possible attack vectors, thus modeling the so-called <em>attack surface<\/em>. And then they methodically test the most promising methods and cross them off one by one until they find an attack that actually works \u2014 one they can use to penetrate the network.<\/p>\n<p>But some attack vectors are harder to exploit than others, and these also usually get cut in the process of modeling the attack surface \u2014 malefactors aren\u2019t willing to waste time and effort trying to use them, and neither was the security researchers team. And some attack vectors have limitations \u2014 they require the attacker to stay physically close to their target, say, and these vectors are also of no particular interest in this case.<\/p>\n<p>That\u2019s why Kaspersky\u2019s ICS CERT guys decided not to look at attacking the Z-Wave protocol \u2014 which the smart home hub uses to talk to the appliances \u2014 because it required the physical presence of the attacker near the house. They also discarded the idea of exploiting the programming language interpreter; the Fibaro hub used the patched version.<\/p>\n<p>Eventually, they succeeded in finding a remote <a href=\"https:\/\/encyclopedia.kaspersky.com\/glossary\/sql-injection\/\" target=\"_blank\" rel=\"noopener noreferrer\">SQL-injection vulnerability<\/a>, despite Fibaro\u2019s significant efforts to avoid them, and a couple of remote code execution vulnerabilities in the PHP code (for more details, <a href=\"https:\/\/securelist.com\/fibaro-smart-home\/91416\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\">read Securelist\u2019s report<\/a>).<\/p>\n<p>If exploited, these vulnerabilities would allow attackers to get root access rights on the smart hub, which basically means getting full control over it. It\u2019s worth noting that even the owner of the hub doesn\u2019t have such access rights and thus won\u2019t be able to override attackers\u2019 actions. But first, attackers need to be able to send commands to the device.<\/p>\n<h3>The flip side of the smart home<\/h3>\n<p>What\u2019s important about the Fibaro smart home is that it can be managed remotely from any location using the cloud. That means vulnerabilities might exist not only in the device itself, but also in the cloud that it uses, and the communication protocols it employs. As it turned out, a severe vulnerability was present in the Fibaro\u2019s cloud, and it allowed the attackers to access all backups uploaded from all Fibaro hubs all around the globe.<\/p>\n<p>That is how the security researchers team acquired backup data stored by the Fibaro Home Center located in this particular home. Among other things this backup contains a database file with a lot of personal information in it \u2014 the house\u2019s location, geolocation data from the owner\u2019s smartphone, the e-mail address used to register with Fibaro, information about the smart devices (Fibaro and non-Fibaro) in the owner\u2019s house, and even the owner\u2019s password.<\/p>\n<p>The password, however, was stored properly, being <a href=\"https:\/\/encyclopedia.kaspersky.com\/glossary\/hashing\/\" target=\"_blank\" rel=\"noopener noreferrer\">hashed<\/a> and <a href=\"https:\/\/encyclopedia.kaspersky.com\/glossary\/salt\/\" target=\"_blank\" rel=\"noopener noreferrer\">salted<\/a>. It could not be decrypted easily, and was of no use to the security researchers. It\u2019s worth noting that if some of the other smart devices required passwords, these passwords were stored in the very same database without any encryption.<\/p>\n<p>The team of security researchers then crafted a special version of the backup that contained a payload in a form of a PHP script that would execute arbitrary commands sent to it remotely. After that, they used a cloud function that let them send e-mails and SMS messages to the owner, telling him something had gone wrong with his smart home and that he needed to apply an update to restore proper function.<\/p>\n<p>Of course, the infosec-savvy person who was already expecting an attack quickly realized that the request was really bait, but the average unsuspecting user probably wouldn\u2019t. So, the smart home owner played along, and that is how the attackers got access to the smart hub, along with all of the smart devices it controlled. Most important, they also gained access to the home network.<\/p>\n<h2>What happens if a smart home gets hacked?<\/h2>\n<p>Once they\u2019ve virtually broken into a smart home, attackers can control all of the smart appliances and devices connected to the home network. In this case, that means they could control the temperature in the house, turn on the sauna, play loud music from the stereo (something they actually did \u2014 they changed the alarm sound to a drum and bass track), print anything on a network printer and so on and so forth.<\/p>\n<p><span class=\"embed-youtube\" style=\"text-align:center; display: block;\"><iframe class=\"youtube-player\" type=\"text\/html\" width=\"640\" height=\"390\" src=\"https:\/\/www.youtube.com\/embed\/cFA4_ZwlM9I?version=3&amp;rel=1&amp;fs=1&amp;showsearch=0&amp;showinfo=1&amp;iv_load_policy=1&amp;wmode=transparent\" frameborder=\"0\" allowfullscreen=\"true\"><\/iframe><\/span><\/p>\n<p>More important, they could remotely open the front door and disable security cameras and motion sensors \u2014 an easy way in to rob the house. And because they knew the coordinates of the owner\u2019s phone, they could plan the operation for when he was far from home.<\/p>\n<p>So, in general, having your smart home hacked may not hurt much, unless the attackers plan on robbing your house and hack it just to disable the security system. The lesson here is, when planning a smart home, don\u2019t rely too heavily on its security features \u2014 they can be disabled.<\/p>\n<p>We also must give some credit to Fibaro Group, which created a rather secure product \u2014 and also worked closely with our ICS Cert researchers to quickly patch the vulnerabilities they discovered. Fibaro Smart Home Centers have become more secure as a result of our little experiment, and we now consider them safe to use.<\/p>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"kis-trial-cyberattacks\">\n","protected":false},"excerpt":{"rendered":"<p>Fibaro Smart Home Centers can be hacked, and the consequences for smart home owners are big.<\/p>\n","protected":false},"author":675,"featured_media":22898,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[2646],"tags":[3146,899,658,794,3147,660],"class_list":{"0":"post-22897","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-threats","8":"tag-fibaro","9":"tag-hack","10":"tag-internet-of-things","11":"tag-iot","12":"tag-kaspersky-ics-cert","13":"tag-smart-home"},"hreflang":[{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/hacking-things\/22897\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/hacking-things\/16079\/"},{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/hacking-things\/13585\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/hacking-things\/6275\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/hacking-things\/17975\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/hacking-things\/16111\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/hacking-things\/14846\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/hacking-things\/18770\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/hacking-things\/17538\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/hacking-things\/23017\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/hacking-things\/6105\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/hacking-things\/27431\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/hacking-things\/11912\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/hacking-things\/11969\/"},{"hreflang":"pl","url":"https:\/\/plblog.kaspersky.com\/hacking-things\/10909\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/hacking-things\/19592\/"},{"hreflang":"ja","url":"https:\/\/blog.kaspersky.co.jp\/hacking-things\/23540\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/hacking-things\/18605\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/hacking-things\/22839\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/www.kaspersky.com.au\/blog\/tag\/internet-of-things\/","name":"Internet of things"},"_links":{"self":[{"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/posts\/22897","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/users\/675"}],"replies":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/comments?post=22897"}],"version-history":[{"count":4,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/posts\/22897\/revisions"}],"predecessor-version":[{"id":23777,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/posts\/22897\/revisions\/23777"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/media\/22898"}],"wp:attachment":[{"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/media?parent=22897"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/categories?post=22897"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.kaspersky.com.au\/blog\/wp-json\/wp\/v2\/tags?post=22897"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}