Not any more safe or dangerous than it was BEFORE the ban frankly. And this applies to Dahua and many other China-made brands. You should isolate ALL IP cameras and IoT devices from the Internet.Not safe to by Hikvision equipment since banned?
There was a backdoor on hikvision cams around 2017 and yes alot of them are still in use, that is indeed concerning as well watchfull_IP disclosed web attack at 2021. But new equipment is as exploitable as anything else that have access to internet.
Personally re Stuxnet .....anything that specifically targets Iranian centrifuges or other equipment is just fine by me.I've said it before, but while I use these brands of cameras on my personal network and don't have anything to fear by doing so, I am also 100% in support of the ban.
Regardless of the political motivations for passing this ban, it actually does help improve our national security. I know a lot of people would argue that a properly set up network would prevent any harm from using these cameras (which is why I use them on my personal network), but that is a short sighted concept of the level of network security that our government and other sensitive faculties needs to be applying. Just look into the Stuxnet virus to see how advanced electronic warfare can be - especially from state sponsored groups that have the money to accomplish almost anything. Stuxnet was a single purpose virus that worked it's way into a secure facility and onto a completely isolated network (ie zero outside connections) without the hackers having physical access to the facility. Imagine how much easier it would have been to accomplish if the hackers could have loaded the virus on a device that was going to be installed in the facility - by the very people who ran the facility! By allowing these cameras into government and other sensitive facilities, we are potentially installing a real trojan horse that would make the hackers job that much easier. The hackers are state sponsored and the companies are (at least partially) state owned - it absolutely could happen and the ban is designed to be just one more layer of a very complex security scheme.
But in case I wasn't clear in the first part of the post, I have no problem using these brands in personal/private networks. This use is not going to be the intended target of a Stuxnet type attack and therefore there is no real risk as long as the devices are isolated on your network (ie they have no access to the internet of the rest of of your network).
How else would i draw you here I guess that workedYou spelt my name wrong! Super offended
I have been outplayed. You win this timeHow else would i draw you here I guess that worked
Since I've been cleverly tricked here by @trempa92 I may as well give my 2 pennies starting by repeating what I said on my CVE-2021-36260 blog post.
Unauthenticated Remote Code Execution (RCE) vulnerability in Hikvision IP camera/NVR firmware (CVE-2021-36260)
This article has been written for a technical audience.watchfulip.github.ioUnauthenticated Remote Code Execution (RCE) vulnerability in Hikvision IP camera/NVR firmware (CVE-2021-36260)
This article has been written for a technical audience.watchfulip.github.io
Never trust any IoT device with Internet access (outbound nor inbound). Assume it's compromised or capable of being compromised. It doesn't matter who makes it, the nationality of that manufacturer, or who supplied it (sold it) to you.
Even just giving it a non-existent gateway is better than nothing (though of course not 100%).
Ideally said devices will be on their own restricted network even internally. Especially in a cooperate environment so that authorised devices and people can talk to them, on whatever ports needed, but the IoT is only permitted to access specific things as required.
That said, I've analysed well over 100 IoT devices by now from different manufacturers, reported many vulnerabilities.
I've never seen something I believed to be a deliberate backdoor placed by the vendor with malicious intent. Most people who found something like that will shout about it clear and loudly. That would be verifiable by others, and where proven hugely damaging to said manufacturer.
Security researchers decrypt encrypted firmware, analyse the code, test network attack surface, defeat device protections to obtain root shell and run unsigned debug tools, monitor network calls pre encryption with gdb/other methods etc. Interface with the hardware using modifications, hardware tools, logic analysers etc where needed. And there's lots of very clever people out there doing that.
A backdoor even if heavily obfuscated has a ticking clock before being publicly exposed - certainly where there are millions of said devices. Even more so where the firmware is easily available including previous versions for analysis.
I'm not saying it cannot or has not ever happen(ed). As I say always assume it is not secure.
There's a lot of media hysteria about these devices made in certain countries. But a clandestine backdoor is going to get exposed assuming it's not narrowly tagetted/deployed on a small subset of specific target devices.
It isn't always obvious if it's a backdoor or a vulnerability. But especially it is obfuscated/has extra code encryption, doesn't show access in logs, stealthed network traffic and not easily assessable (say a private RSA key or similar is needed) then that's going to be potentially disastrous if you are a multi billion dollar international manufacturer of those devices when it is exposed. Too many damn security researchers poking their noses in
(I place Internet network backbone devices in a much more sensitive category, given its functional role it has Internet access, and huge volumes of traffic as well as not always being available for reasonable purchase for independent security analysis).
If you are a particularly sensitive target, then a hardware supply chain attack may more likely where you are supplied with specifically compromised equipment without knowing. Countries have done that against specific targets in the past. I'd also only update offline, using firmware everyone else is using, as opposed to an online update where the device could be targeted by update servers and fed a specially compromised update.
If you are enriching uranium for potential use in nuclear weapons, yes be careful where you buy your cameras from
Have done this many times with TVs......why the hell does a Samsung TV need to send data to China and India? Yet, there it was, establishing a session with who knows whom.....then it's a simple...relatively......matter to set up a firewall rule to deny IP block addresses to specific places.
Devices may be contacting infrastructure anywhere in the world that may be totally legitimate. Some people will misinterpret that as phoning home for some dark purpose when it's actually totally innocent. DNS, NTP and update checking is common of course, as are checking to see if the device is registered on a remote access platform for customer use. Ideally the last should be already disabled by default and needs customer to turn on.Best thing to do is run a Wireshark session when you plug the device into the network. Set it up to be logged and then at your leisure look thru the log later after you've unplugged the device from the network for analysis. Problem is network analysis is not a simple thing and Wireshark is not intuitive but it's very, very good.
Have done this many times with TVs......why the hell does a Samsung TV need to send data to China and India? Yet, there it was, establishing a session with who knows whom.....then it's a simple...relatively......matter to set up a firewall rule to deny IP block addresses to specific places.
Can be said as much about any other IoT as numerous posts above explained already.Be aware, whether you purchase Dahua, Hikvision, or any other mid-range or even no-name camera, some of the firmwares have hacks/workarounds for invalid gateways, invalid DNS, etc. There have been documented instances where these devices embed hard-coded IP addresses into their firmware, specifically for this purpose. Quite determined, they are.
Can be said as much about any other IoT as numerous posts above explained already.
Would you be kind and share documentation or any topic regarding where was mentions of hardcoded ip addresses inside firmware? Its not that I ask for a proof of your statement is that it actually interests me, as I mainly work with hikvision.
Thats a wierd one, heard a lot of funny stories myself, some seen myself, some were told by others(cant be confirmed).I recall there was a post a few years back where someone had changed the camera IP address subnet to something completely different than the default IP subnet and yet wireshark was showing the camera was still trying to access the internet via the 192.168.1.xxx subnet and would have had his system had that as a subnet, which most people are lazy and use the default IP address subnet the router gives them.
Now to find that thread LOL!
Can be said as much about any other IoT as numerous posts above explained already.
Would you be kind and share documentation or any topic regarding where was mentions of hardcoded ip addresses inside firmware? Its not that I ask for a proof of your statement is that it actually interests me, as I mainly work with hikvision.
Setting an invalid gateway really doesn't do anything useful. It's just a false sense of security. If you're trying to protect against the camera running malicious software, an invalid gateway would be trivially bypassed by the malware by just scanning the network for routers. Also, setting an invalid gateway is not doable with IPv6, as IPv6 routes are configured using Router Advertisement broadcasts.invalid gateways, invalid DNS, etc
.... 2 network cards in your BI machineSetting an invalid gateway really doesn't do anything useful. It's just a false sense of security. If you're trying to protect against the camera running malicious software, an invalid gateway would be trivially bypassed by the malware by just scanning the network for routers. Also, setting an invalid gateway is not doable with IPv6, as IPv6 routes are configured using Router Advertisement broadcasts.
Cameras should always be on a separate VLAN that does not have internet access, regardless of brand or country of manufacture. The firewall on your router should be configured to allow inbound cross-VLAN connections from your regular VLAN to the camera VLAN, but not the other way around (i.e. your PC or Blue Iris server can access the camera, but the camera can't access them).