{"id":21264,"date":"2023-06-20T08:19:08","date_gmt":"2023-06-20T12:19:08","guid":{"rendered":"https:\/\/me-en.kaspersky.com\/blog\/pet-feeders-vulnerabilities\/21264\/"},"modified":"2023-06-20T19:55:36","modified_gmt":"2023-06-20T15:55:36","slug":"pet-feeders-vulnerabilities","status":"publish","type":"post","link":"https:\/\/me-en.kaspersky.com\/blog\/pet-feeders-vulnerabilities\/21264\/","title":{"rendered":"Hole in the bowl: smart pet feeder springs a leak"},"content":{"rendered":"<p>All animal owners love their pets. And what do pets love above all else? TLC and food, of course. Or vice versa: food first, tummy-rub second.<\/p>\n<p>Today\u2019s smart feeders are designed to make sure your pet won\u2019t go hungry or get bored while you\u2019re away. But what\u2019s the score cybersecurity-wise? Not great\u2026<\/p>\n<h2>Smart feeder for furry friends<\/h2>\n<p>Smart feeders are becoming a popular choice for pet owners who can\u2019t stay at home all day. It\u2019s hard to explain to a cat or dog why you need to leave the house every morning instead of staying home to feed and walk\/play with them, but at least with a smart feeder \u2014 they don\u2019t go hungry.<\/p>\n<p>The earliest smart feeders were offline timer-controlled devices that simply measured out food portions. But, as smart-home systems caught on, feeders became more complicated and acquired extra features. Now, not only can you set a food-dispensing schedule, but also monitor and even communicate remotely with your pet using the built-in microphone, speaker and camera; many also support voice control via external devices such as Amazon Alexa. For this, they connect to your home Wi-Fi and are managed through an app on your phone.<\/p>\n<p>As you can guess, if a smart-home device has camera, microphone and internet access, it\u2019s of great interest to hackers. As regards IP camera security (or lack thereof), we\u2019ve already <a href=\"https:\/\/www.kaspersky.com\/blog\/ip-cameras-unsecurity-eufy\/46574\/\" target=\"_blank\" rel=\"noopener nofollow\">used up a lot of digital ink;<\/a>\u00a0hackers can hijack online baby monitors to <a href=\"https:\/\/whdh.com\/news\/take-your-clothes-off-hacker-uses-security-system-to-talk-to-nanny-children-inside-home\/\" target=\"_blank\" rel=\"nofollow noopener\">harass babysitters and frighten kids<\/a>; robot vacuum cleaners can <a href=\"https:\/\/www.kaspersky.com\/blog\/robot-vacuum-privacy\/46682\/\" target=\"_blank\" rel=\"noopener nofollow\">leak racy photos of owners<\/a> or a layout of their home; and even smart light bulbs (!) have been used for <a href=\"https:\/\/www.usatoday.com\/story\/tech\/2020\/02\/05\/how-to-avoid-smart-lights-getting-hacked\/4660430002\/\" target=\"_blank\" rel=\"nofollow noopener\">attacks on home networks<\/a>.<\/p>\n<p>Now it\u2019s smart feeders\u2019 turn.<\/p>\n<h2>Leaky bowl<\/h2>\n<p>Our experts studied the popular <a href=\"https:\/\/finance.yahoo.com\/news\/dogness-intelligent-pet-products-climb-123000676.html\" target=\"_blank\" rel=\"nofollow noopener\">Dogness smart feeder<\/a> and found many vulnerabilities in it that allow an attacker to alter the feeding schedule \u2014 potentially endangering the health of your pet, or even to turn the feeder into a spying device. Some of the more frustrating security issues include the use of hard-coded credentials, communication with the cloud in cleartext, and an insecure firmware update process. These vulnerabilities can be leveraged to gain unauthorized access to the smart feeder and use it as a launching pad to attack other devices on the home network. For details about the research methodology, see <a href=\"https:\/\/securelist.com\/smart-pet-feeder-vulnerabilities\/110028\/\" target=\"_blank\" rel=\"noopener\">our in-depth report<\/a> on Securelist. Here though, we\u2019ll just touch on what holes were found and the risks they pose.<\/p>\n<h2>The root of the problem<\/h2>\n<p>The main vulnerability in the Dogness smart feeder is the Telnet server allowing remote root access through the default port. At the same time, the <a href=\"https:\/\/encyclopedia.kaspersky.com\/glossary\/root-access\/\" target=\"_blank\" rel=\"noopener\">superuser password<\/a> is hard-coded in the firmware and cannot be changed, meaning that an attacker who extracts the firmware can easily recover the password and gain full access to the device\u00a0\u2014 and in fact <em>any<\/em> device of the same model, since they all have the same root password. All they have to do is buy the same model of feeder and tinker around with it.<\/p>\n<p>By logging in remotely via Telnet (for this the hacker needs to gain remote access to your home network) with root access, an intruder can execute any code on the device, change the settings and steal sensitive data, including video footage transferred from the feeder camera to the cloud. Thus, the feeder can readily be transformed into a snooping device with a wide-angle camera and a good microphone.<\/p>\n<h2>Encryption anyone?<\/h2>\n<p>In addition to the root password being both embedded in the firmware and common for all devices, we discovered a no less serious vulnerability: the feeder communicates with the cloud without any encryption. Authentication data is likewise transmitted in unencrypted form, which means a malicious actor doesn\u2019t even have to bother scraping the root password from the firmware: it suffices to intercept the traffic between the feeder and the cloud, gain access to the device, then attack other devices on the same network through it \u2014 which puts the entire home infrastructure at risk.<\/p>\n<h2>Alexa, bark!<\/h2>\n<p>But despite the holes, the bowl is still full of surprises. The Dogness feeder can connect to Amazon Alexa for voice control. Handy, right? Just say \u201cFeed!\u201d to Alexa. You don\u2019t even need to get your phone out.<\/p>\n<p>Once again, as you can imagine, such lax security on the part of the developers has consequences. The device receives commands from Alexa via MQTT (Message Queuing Telemetry Transport), and the login credentials are again written in cleartext directly in the executable file. Which again means they\u2019re the same for all devices on the market \u2014 that is, once you connect your feeder to Alexa for voice control, it\u2019s not really <em>your<\/em> feeder anymore.<\/p>\n<p>By connecting to the MQTT server, a hacker can quickly collect the identifiers of all similar devices connected to the server \u2013 that is, all those feeders whose owners decided to use the voice control. After that, the cybercriminal can send any of the commands available via voice control from the MQTT server to any Alexa-connected Dogness feeder with a known identifier.<\/p>\n<p>A cybercriminal would be able to send it commands to change the feeding schedule and amounts of measured-out food (granting your pet either a feast fit for a king or a Jesus-like fast). Another side-effect is that an attacker could send specially formed commands to the feeder repeatedly, thereby rendering the voice command interface inoperable.<\/p>\n<h2>Streaming \u2014 whether you want it or not<\/h2>\n<p>As the study progressed, new surprises awaited us regarding the uploading of video to the cloud, from where you can stream it back to your phone. Although the mobile app connects to the server using the secure HTTPS protocol, it turned out that the feeder itself transmits data to the cloud without any encryption at all \u2014 via bad old HTTP. What\u2019s more, both the device ID and the upload key (which is hardcoded into the binary) are transmitted to the server in cleartext.<\/p>\n<p>Given that the feeder camera is designed to continuously record and transmit video to the server, this vulnerability allows attackers to see and hear everything that goes on in the camera\u2019s field of view.<\/p>\n<h2>Not-so-firm ware<\/h2>\n<p>Finally, the icing on the cake; rather \u2014 the cream that the cat got: the firmware update process \u2014 the means by which to fix the above issues \u2014 is itself insecure! To update, the feeder downloads an archive file with new firmware from the update server via the unsafe HTTP. Yes, the archive is password-protected, but, as you\u2019ve probably already guessed, this password is written in cleartext in one of the update scripts. And the URL from which the latest firmware version is downloaded is generated based on the response received from the update server, whose address is, that\u2019s right, stitched into the existing firmware.<\/p>\n<p>There are no digital signatures, and no other methods of verifying the firmware: the device downloads the archive with the new firmware over an unencrypted channel, unzips it using the embedded (and common to all devices) password, and promptly installs it. This means that an attacker can potentially modify the firmware and upload anything they wish to the device \u2014 adding unexpected and unwanted features.<\/p>\n<h2>How to stay safe?<\/h2>\n<p>In an ideal world, all these security flaws would have been remedied by the feeder manufacturer through a timely firmware update \u2014 before hackers got to know about them. Back in the real world, we\u2019ve repeatedly reported the flaws to said manufacturer, but have had no response \u2014 since October 2022. Meanwhile, all the vulnerabilities we found are still there in the Dogness smart feeders that are being sold to the public. And this poses a serious threat to pets\u2019 well-being and owners\u2019 privacy.<\/p>\n<p>We recommend reading our <a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-secure-smart-home\/47472\/\" target=\"_blank\" rel=\"noopener nofollow\">detailed guide to setting up smart-home security<\/a>. Most of the advice there applies equally to the smart-feeder issues described above. In any case, here are some simple tips specifically for owners of Dogness feeders:<\/p>\n<ul>\n<li>Check regularly for firmware updates.<\/li>\n<li>Don\u2019t use Amazon Alexa to control your Dogness feeder.<\/li>\n<li>Either turn off video streaming to the cloud, or position the feeder in your home so that the camera can\u2019t capture anything private.<\/li>\n<li><a href=\"https:\/\/www.kaspersky.com\/blog\/how-to-use-vpn-on-routers\/48410\/\" target=\"_blank\" rel=\"noopener nofollow\">Set up a secure VPN connection to access the internet using a router<\/a> that supports your home network \u2014 this will greatly reduce the risk of attacks via the insecure HTTP protocol.<\/li>\n<li>If your router doesn\u2019t have VPN support, create a guest Wi-Fi network on it and connect the feeder (and other insecure smart-home devices) to it. This will prevent attacks on other parts of your home network if an insecure smart device gets hacked.<\/li>\n<li>Use a reliable security solution on all devices in your home. We recommend a <a href=\"https:\/\/me-en.kaspersky.com\/premium?icid=me-en_bb2022-kdplacehd_acq_ona_smm__onl_b2c_kdaily_lnk_sm-team___kprem___\" target=\"_blank\" rel=\"noopener\">Kaspersky Premium<\/a> subscription for comprehensive protection of all devices in your home. Included is <a href=\"https:\/\/me-en.kaspersky.com\/vpn-secure-connection?icid=me-en_kdailyplacehold_acq_ona_smm__onl_b2c_kasperskydaily_wpplaceholder____vpn___\" target=\"_blank\" rel=\"noopener\">high-speed VPN access with unlimited bandwidth<\/a>, plus monitoring of changes on your home network to detect and reject unauthorized connections.<\/li>\n<\/ul>\n<input type=\"hidden\" class=\"category_for_banner\" value=\"premium-family\">\n","protected":false},"excerpt":{"rendered":"<p>Smart feeders were invented to make life easier for pet owners; however, their vulnerabilities threaten not only owners\u2019 privacy, but also the health of their pets.<\/p>\n","protected":false},"author":2742,"featured_media":21265,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1486],"tags":[2088,82,765,43,97,630,1144,521,174],"class_list":{"0":"post-21264","1":"post","2":"type-post","3":"status-publish","4":"format-standard","5":"has-post-thumbnail","7":"category-threats","8":"tag-tips","9":"tag-hacking","10":"tag-iot","11":"tag-privacy","12":"tag-security-2","13":"tag-smart-home","14":"tag-technologies","15":"tag-threats","16":"tag-wi-fi"},"hreflang":[{"hreflang":"en-ae","url":"https:\/\/me-en.kaspersky.com\/blog\/pet-feeders-vulnerabilities\/21264\/"},{"hreflang":"en-in","url":"https:\/\/www.kaspersky.co.in\/blog\/pet-feeders-vulnerabilities\/25823\/"},{"hreflang":"ar","url":"https:\/\/me.kaspersky.com\/blog\/pet-feeders-vulnerabilities\/10789\/"},{"hreflang":"en-us","url":"https:\/\/usa.kaspersky.com\/blog\/pet-feeders-vulnerabilities\/28521\/"},{"hreflang":"en-gb","url":"https:\/\/www.kaspersky.co.uk\/blog\/pet-feeders-vulnerabilities\/26122\/"},{"hreflang":"es-mx","url":"https:\/\/latam.kaspersky.com\/blog\/pet-feeders-vulnerabilities\/26472\/"},{"hreflang":"es","url":"https:\/\/www.kaspersky.es\/blog\/pet-feeders-vulnerabilities\/28954\/"},{"hreflang":"it","url":"https:\/\/www.kaspersky.it\/blog\/pet-feeders-vulnerabilities\/27872\/"},{"hreflang":"ru","url":"https:\/\/www.kaspersky.ru\/blog\/pet-feeders-vulnerabilities\/35605\/"},{"hreflang":"tr","url":"https:\/\/www.kaspersky.com.tr\/blog\/pet-feeders-vulnerabilities\/11557\/"},{"hreflang":"x-default","url":"https:\/\/www.kaspersky.com\/blog\/pet-feeders-vulnerabilities\/48461\/"},{"hreflang":"fr","url":"https:\/\/www.kaspersky.fr\/blog\/pet-feeders-vulnerabilities\/20764\/"},{"hreflang":"pt-br","url":"https:\/\/www.kaspersky.com.br\/blog\/pet-feeders-vulnerabilities\/21462\/"},{"hreflang":"de","url":"https:\/\/www.kaspersky.de\/blog\/pet-feeders-vulnerabilities\/30282\/"},{"hreflang":"ru-kz","url":"https:\/\/blog.kaspersky.kz\/pet-feeders-vulnerabilities\/26439\/"},{"hreflang":"en-au","url":"https:\/\/www.kaspersky.com.au\/blog\/pet-feeders-vulnerabilities\/32132\/"},{"hreflang":"en-za","url":"https:\/\/www.kaspersky.co.za\/blog\/pet-feeders-vulnerabilities\/31816\/"}],"acf":[],"banners":"","maintag":{"url":"https:\/\/me-en.kaspersky.com\/blog\/tag\/threats\/","name":"threats"},"_links":{"self":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/21264","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/users\/2742"}],"replies":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/comments?post=21264"}],"version-history":[{"count":2,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/21264\/revisions"}],"predecessor-version":[{"id":21267,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/posts\/21264\/revisions\/21267"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media\/21265"}],"wp:attachment":[{"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/media?parent=21264"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/categories?post=21264"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/me-en.kaspersky.com\/blog\/wp-json\/wp\/v2\/tags?post=21264"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}