{"id":6939,"date":"2017-03-10T13:17:31","date_gmt":"2017-03-10T21:17:31","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2017\/03\/10\/news-730\/"},"modified":"2017-03-10T13:17:31","modified_gmt":"2017-03-10T21:17:31","slug":"news-730","status":"publish","type":"post","link":"http:\/\/www.palada.net\/index.php\/2017\/03\/10\/news-730\/","title":{"rendered":"Dahua, Hikvision IoT Devices Under Siege"},"content":{"rendered":"

Credit to Author: BrianKrebs| Date: Fri, 10 Mar 2017 20:07:51 +0000<\/strong><\/p>\n

Dahua<\/strong>, the world’s second-largest maker of “Internet of Things” devices like security cameras and digital video recorders (DVRs), has shipped a software update that closes a gaping security hole in a broad swath of its products. The vulnerability allows anyone to bypass the login process for these devices and gain remote, direct control over vulnerable systems. Adding urgency to the situation, there is now code available online that allows anyone to exploit this bug and commandeer a large number of\u00a0IoT devices.<\/p>\n

\"dahua\"On March 5, a security researcher named Bashis<\/strong> posted to the Full Disclosure security mailing list<\/a> exploit code for an embarrassingly simple flaw in the way many Dahua security cameras and DVRs handle authentication. These devices are designed to be controlled by a local Web server that\u00a0is accessible via a Web browser.<\/p>\n

That server requires the user to enter a username and password, but Bashis found he could force all affected devices to cough up their usernames and a simple hashed value of the password. Armed with this information, he could effectively “pass the hash” and the corresponding username right back to the Web server and be admitted access to the device settings page. From there, he could add users and install or modify the device’s software. From Full Disclosure:<\/p>\n

\n

“This is so simple as:
1. Remotely download the full user database with all credentials and permissions
2. Choose whatever admin user, copy the login names and password hashes
3. Use them as source to remotely login to the Dahua devices<\/p>\n

“This is like a damn Hollywood hack, click on one button and you are in…”<\/p>\n<\/blockquote>\n

Bashis said he was so appalled at the discovery that he labeled it an\u00a0apparent “backdoor” — an undocumented means of accessing an electronic device that often only the vendor\u00a0knows about. Enraged, Bashis decided to publish his exploit code without first notifying Dahua. Later, Bashis said he changed his mind after being contacted by the company and agreed\u00a0to remove his code from the online posting.<\/p>\n

Unfortunately, that ship may have already sailed. Bashis’s exploit code already has been copied in several other places online as of this publication.<\/p>\n

Asked why he took down his exploit code, Bashis said in an interview with KrebsOnSecurity that “The hack is too simple, way too simple, and now I want Dahua’s users to get patched firmware\u2019s before they will be victims to some botnet.”<\/p>\n

In an advisory published March 6, Dahua said it has identified nearly a dozen of its products that are vulnerable, and that further review may reveal additional models also have this flaw. The company is urging users to download and install the newest firmware updates<\/a> as soon as possible. Here are the models known to be affected so far:<\/p>\n

DH-IPC-HDW23A0RN-ZS
DH-IPC-HDBW23A0RN-ZS
DH-IPC-HDBW13A0SN
DH-IPC-HDW13A0SN
DH-IPC-HFW13A0SN-W
DH-IPC-HDBW13A0SN
DH-IPC-HDW13A0SN
DH-IPC-HFW13A0SN-W
DHI-HCVR51A04HE-S3
DHI-HCVR51A08HE-S3
DHI-HCVR58A32S-S2<\/p>\n

It’s not clear exactly how many devices worldwide may be vulnerable. Bashis says that’s a difficult question to answer, but that he “wouldn’t be surprised if 95 percent of Dahua’s product line has the same problem,” he said. “And also possible their OEM clones.”<\/p>\n

Dahua has not yet responded to my questions or request for comment. I’ll update that here if things change on that front.<\/p>\n

This is the second time in a week that a major Chinese IoT firm has urgently warned its\u00a0customers to update the firmware on their devices. For weeks, experts have been warning that there are signs of attackers exploiting an unknown backdoor or equally serious vulnerability in cameras and DVR devices made by IoT giant Hikvision<\/strong>.<\/span><\/p>\n

Writing for video surveillance publication IPVM<\/strong>, Brian Karas<\/strong> reported on March 2<\/a> that he was hearing from multiple Hikvision security camera and DVR users who suddenly were locked out of their devices and had new “system” user accounts added without their permission.<\/p>\n

Karas said the devices in question all were set up to be remotely accessible over the Internet, and were running with the default credentials (12345). Karas noted that there don’t appear to be any Hikvision devices sought out by the Mirai worm<\/a> — the now open-source malware<\/a>\u00a0that is being used to enslave IoT devices in a botnet for launching crippling online attacks (in contrast, Dahua’s products are hugely represented in the list of systems being sought out by the Mirai worm<\/a>.)<\/p>\n

In addition, a\u00a0programmer who has long written and distributed custom firmware for Hikvision devices claims he’s found a backdoor\u00a0in “many popular Hikvision products that makes it possible to gain full admin access to the device,” wrote<\/a> the user “Montecrypto” on the IoT forum IPcamtalk<\/strong> on Mar. 5. “Hikvision gets two weeks to come forward, acknowledge, and explain why the backdoor is there and when it is going to be removed. I sent them an email. If nothing changes, I will publish all details on March 20th, along with the firmware that disables the backdoor.”<\/p>\n

According to IPVM’s Karas, Hikvision has not acknowledged an unpatched backdoor or any other equivalent weakness in its product. But on Mar. 2, the company issued a reminder to its integrator partners about the need to be updated to the latest firmware.<\/p>\n

\"A<\/p>\n

A special bulletin issued Mar. 2, 2017 by Hikvision. Image: IPVM<\/p>\n<\/div>\n

“Hikvision has determined that there is a scripted application specifically targeting Hikvision NVRs and DVRs that meet the following conditions: they have not been updated to the latest firmware; they are set to the default port, default user name, and default password,” the company’s statement reads. “Hikvision has required secure activation since May of 2015, making it impossible for our integrator partners to install equipment with default settings. However, it was possible, before that date, for integrators to install NVRs and DVRs with default settings. Hikvision strongly recommends that our dealer base review the security levels of equipment installed prior to June 2015 to ensure the use of complex passwords and upgraded firmware to best protect their customers.”<\/p>\n

ANALYSIS<\/h4>\n

I don’t agree with Bashis’s conclusion that the Dahua flaw was intentional; It appears that the makers of these products simply did not invest much energy, time or money in building security into the software. Rather, security is clearly an afterthought that is bolted on afterwards with these devices, which is why nobody should trust them.<\/p>\n

The truth is that the software that runs on a whole mess of these security cameras and DVRs is very poorly written, and probably full of more security holes just like the flaw Dahua users are dealing with right now. To hope or wish otherwise given what we know about the history of these cheap electronic devices seems sheer folly.<\/p>\n

In December, KrebsOnSecurity warned<\/a> that many Sony security cameras contained a backdoor that can only be erased by updating the firmware on the devices.<\/p>\n

Some security experts maintain that these types of flaws can’t be easily exploited when the IoT device in question is behind a firewall. But that advice just doesn’t hold water for today’s IoT cameras and DVRs. For one thing, a great many security cameras and other IoT devices will punch a hole in your firewall straight away without your permission, using a technology called Universal Plug-and-Play<\/a> (UPnP).<\/p>\n

In other cases, IoT products are incorporating peer-to-peer (P2P) technology that cannot be turned off<\/a> and exposes users to even greater threats. \u00a0In that same December 2016 story referenced above, I cited research from security firm Cybereason<\/strong>, which found at least two previously unknown security flaws in dozens of IP camera families that are white-labeled under a number of different brands (and some without brands at all).<\/p>\n

“Cybereason\u2019s team found that they could easily exploit these devices even if they were<\/em> set up behind a firewall,” that story noted. “That\u2019s because all of these cameras ship with a factory-default peer-to-peer (P2P) communications capability that enables remote ‘cloud’ access to the devices via the manufacturer\u2019s Web site \u2014 provided a customer visits the site and provides the unique camera ID stamped on the bottom of the devices.”<\/p>\n

The story continued:<\/p>\n

“Although it may seem that attackers would need physical access to the vulnerable devices in order to derive those unique camera IDs, Cybereason\u2019s principal security researcher Amit Serper<\/strong> said the company figured out a simple way to enumerate all possible camera IDs using the manufacturer\u2019s Web site.”<\/p>\n

My advice? Avoid the P2P models like the plague. If you have security cameras or DVR devices that are connected to the Internet, make sure they are up to date with the latest firmware. Beyond that, consider completely blocking external network access to the devices and enabling a VPN if you truly need remote access to them.<\/p>\n

Howtogeek.com<\/a> has a decent tutorial on setting up your own VPN to enable remote access to your home or business network; on picking a decent router that supports VPNs; and installing custom firmware like DD-WRT on the router if available (because, as we can see, stock firmware usually is some horribly insecure and shoddy stuff).<\/p>\n

If you\u2019re curious about an IoT device you purchased and what it might do after you\u00a0connect it to a network,\u00a0the information is there if you know how and where to look. This Lifehacker post<\/a> walks through some of the basic software tools and steps that even a novice can follow to learn more about what\u2019s going on across a local network.<\/p>\n

https:\/\/krebsonsecurity.com\/feed\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/p>\n

Credit to Author: BrianKrebs| Date: Fri, 10 Mar 2017 20:07:51 +0000<\/strong><\/p>\n

Dahua, the world’s second-largest maker of “Internet of Things” devices like security cameras and digital video recorders (DVRs), has shipped a software update that closes a gaping security hole in a broad swath of its products. The vulnerability allows anyone to bypass the login process for these devices and gain remote, direct control over vulnerable systems. Adding urgency to the situation, there is now code available online that allows anyone to exploit this bug and commandeer a large number of IoT devices.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[10643,10642],"tags":[11601,11602,11603,11604,11605,11606,11607,11608,11609,11610,10644,11611,11612],"class_list":["post-6939","post","type-post","status-publish","format-standard","hentry","category-independent","category-krebs","tag-amit-serper","tag-bashis","tag-cybereason","tag-dahua-backdoor","tag-dh-ipc-hdbw13a0sn","tag-dh-ipc-hdbw23a0rn-zs","tag-dh-ipc-hdw13a0sn","tag-dh-ipc-hdw23a0rn-zs","tag-dh-ipc-hfw13a0sn-w","tag-hikvision","tag-other","tag-p2p","tag-upnp"],"_links":{"self":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/6939","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=6939"}],"version-history":[{"count":0,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/6939\/revisions"}],"wp:attachment":[{"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=6939"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=6939"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=6939"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}