Interview With Researcher Who Cracked Security Of 70+ DVR Brands

By Brian Karas, Published Jul 07, 2016, 09:00am EDT

[link no longer available]The researcher who found an exploit in 70+ brands of TVT OEM DVRs, which he suspected to be the entry point hackers used to gain access to several retailers, elaborated on these hacks to us.

We got in touch with Rotem Kerner [link no longer available], previously a security researcher at RSA, and now co-founder of security research company Cybewrite to discuss the exploitability of embedded security devices.  

Old **** ******* *** * ***** ******

****** **** **** ** feels ************* ** ******** devices **** ********* "****** on *** **** **** not * *** ** people *** ****** ** hack ****". ******** ** other ******** ******* **** print ******* ** ***** *******, ******** cameras *** ********* *** not **** ****** ** many ***** ********, *** accessible ** ********, ****** manufacturers **** ********* ***** their ********.  

Now ****** ********

*** ******* ******* *** exploitable *******, ******** ******* were low-value *******, ** ***** up ***** *** **** few *****. **** *** massive **** ** ** camera ******* *** ********* deployment ** ********-********* ******* they have ****** *********, *** easy, *******.

Worse ** ***** ******* ** ********

** ***** ******* ***** rely ** *** **** core ****** *** ******** http ******* *** ************* *** management.  **** *** **** vulnerabilities ***** ** *** device *********** ********** ** other ******/******** ***** *** same ******** ******** *********.  Another ****** ************* ****** showed ******* ******* ** ******** device ****** *** ******* common ********.

How *************** *** *****

***** ***** ****** ** downloading ******** ******, *** using ***** **** ******* ** ********* **** *** look ** *** *** ***** in *** ********.  **** runs ******** ** *** ************ ********** of scanning * ****** ************ for **** ***** *** trying ******** ******* **** *** ********** ** *** ************.    

********* ** **** ** the *** *****, ************* *** ******** files ********, **** ********* a ********* **** ** brands/logos.  **** ******* *** to *********** ********* **** the ******* ** ******* could ** ******* ** thousands ** ******** ******* from **** ** ******.

Two ****** ******* ** ******* ********

** ******* *** ** installed ** * ****** by ******* **** ** shell ****** ** * linux ******* *** **** downloading **** ******** **** the **** **** * remote ******. **** ****** requires *** ****** ** be **** ** *** network ****** ** *** unit (****** *******, ** over *** ********).  ** has *** ******* ** being **** ** ** done ******* *** **** having ** ** ********, but ********** *** ******* to ********** ******** ** private ******** ** ***** that *** ********** ********.

******* *** ** *** an ******* **** * unit ** ** ********* new ******** *** *** device **** *** *** exploit ***** **, *** then ********* **** ******** onto *** ****. **** can **** ** **** remotely, ** *** ****** can *** *** *** the **** ** ******* the ******** **********. *** way ** ******** * user ** ******* *********** firmware ** ** **** the ******** ********* *** download, *** **** **** an ***** **** ******* to **** **** *** manufacturers ******* ********** ********** a ******** ******.

Securing **** *******

** ** ********** ** fully ****** * ****** connected ** *** ********, but *** *** ****** your ******* ** ****** by ********* ***** **********: 

  1. ****** ******* *********, *** usernames ** *** ****** allows **.  ****** ******** "admin" ** "*****" **** foil ****** ********** ****** ********.
  2. **** ******** ******** ***** from ************* ********, ***** this **** *** ********* files *** *** ***********, it **** ****** *** chances ** ******* ***** firmware.
  3. **** ******** ******* ** prevent *** ******** **** being ****, ******** **** the ************ ** ******* up **** ******** *******.
  4. ***** *** ** *********/******** that *** ****** **** equipment, ** ****** *** close ****** ******** ****** and ******* *** ***.

** *** ****** **** ******** ************* ************, ********** ******** ****** to ******* *** ****** risk ** *******.

What ************* *** **

******** ****** *** *** software **** *** ******** eliminates *** *** **** common ******* ** *******. ******* or ***** ****** ** rarely ****** ** ********** use *****, *** ** often **** ** ******* to **** ****** ** the ******.

************ ******** ********* ******** before ************ ******* * ***** attack ******. **** ******* ** not ****** *** ********* of ******** ***** ****** installing ****, ******** ********* to ****** ***** ******** ****** which *** **** ***** devices **** *********** ******* access *****.

********** *** ******** ***** can **** **** ** more ********* *** ******* to ********* **** *** check *** **** *** exploitable **********.

Comments (19)

Avatar

Jon Dillabaugh

Pro Focus LLC
07/07/16 05:46pm

Nice article. If we kee pushing the industry and best practices, these types of hacks will surely be minimized. Manufacturers, of course, play a large role here, but integrators have to do their part too. VPNs aren't always an option. Sometimes a device needs to be public facing. Restricting the access to that public facing device and monitoring traffic to it is essential.

Agree: 2
Disagree
Informative: 2
Unhelpful
Funny

Undisclosed #1

IPVMU Certified | 07/07/16 07:29pm

Like it!

Confused about this though:

This allowed him to immediately determine that the exploit he created could be applied to thousands of deployed devices from over 70 brands...

An exploit can be installed on a device by gaining root or shell access to a linux console and then downloading code directly into the unit from a remote server.

Isn't the 'exploit' the ability to 'gain root' in the first place?

Sounds to me like you are saying, "Cars can be stolen by using the key to start the engine."

Agree: 2
Disagree
Informative
Unhelpful
Funny
Avatar

Brian Karas

IPVM | In reply to Undisclosed #1 | 07/07/16 06:42pm

Isn't the 'exploit' the ability to 'gain root' in the first place?

In some sense, yes. In this case I was referring more to the exploit being the unintended code that was uploaded to the device and then executed by the device. But just the act of gaining root/shell access is also a form of exploit.

Agree
Disagree
Informative
Unhelpful
Funny

Undisclosed Manufacturer #2

In reply to Undisclosed #1 | 07/07/16 07:43pm

Isn't the 'exploit' the ability to 'gain root' in the first place?

Semantics, but as I see it, the ability to gain unauthorized "root" is the hack. The "exploit" is the change/action you make/take (usually nefarious) as a result of gaining unauthorized access-often installing malware.

Agree: 2
Disagree: 2
Informative
Unhelpful
Funny

Undisclosed #1

IPVMU Certified | In reply to Undisclosed Manufacturer #2 | 07/07/16 07:26pm

The "exploit" is the change/action you make/take (usually nefarious) as a result of gaining unauthorized access-often installing malware.

Disagree. Though that makes sense in the common understanding of the word 'exploit', I don't think that is the usual meaning in cyber-security.

For instance if I use a brute force password program to gain root to a system and then I burn a DVD of all the credit card numbers, the exploit is brute force password attack, not copying files.

This makes sense, since otherwise the exploit could be any number of things, that could be done once you are root.

In this particular case, the result of "exploit he created" is nothing more than the root access itself. This is the usual meaning.

Agree: 1
Disagree
Informative
Unhelpful
Funny

Undisclosed Manufacturer #2

07/07/16 07:47pm

This was one of the two researchers whom I originally thought may have uncovered the Axis vulnerability. I ruled him out on that one and am happy to see this kind of coverage on IPVM.

Agree
Disagree
Informative
Unhelpful
Funny

jason oneal

07/08/16 02:41pm

Is there a way to know if a device has already been compromised? Or will defaulting and then upgrading to latest firmware eliminate any rogue hack placed on the device?

Agree
Disagree
Informative
Unhelpful
Funny
Avatar

Brian Karas

IPVM | In reply to jason oneal | 07/08/16 02:39pm

This is an excellent question.

The generally accepted answer is that there is no way to know for sure if a device has been compromised, especially when it comes to things like cameras where tools like chkrootkit are not yet adapted.

Defaulting a camera will only erase user-configured settings in most cases, it won't wipe out any rogue software that has been added.

The good part is that for most devices the firmware contains a complete image, operating system and all additional files/software needed to run the camera or recorder. Upgrading firmware should do a complete wipe and overwrite any malware. However, just like configuration settings can be saved across a firmware upgrade, so could installed malware if the hackers were particularly sophisticated and understood the internals of the device fully.

I do not think we are at the stage where malware targeted to cameras and recorders is at the point where it can survive across a reset/default and a firmware upgrade, but it is technically possible for this to occur. Hopefully we will see more advanced firmware and code checking implemented by manufacturers before the hackers get ahead of them in this regard.

Agree
Disagree
Informative: 1
Unhelpful
Funny

Andrew Tierney

In reply to Brian Karas | 04/08/17 12:13pm

I've got backdoors for DVRs that persist through a firmware upgrade. Most firmware updates don't touch the bootloader.

Agree
Disagree
Informative
Unhelpful
Funny

Michael Henderson

07/12/16 05:24pm

Considering the brands hacked, maybe it is time to quit selling the low end crap and start designing systems and networks with actual security in mind. You know, that thing we are supposed to do in the beginning.

Salespeople need to quit being price conscious and start selling the service expected of our industry. If end users are so price sensitive, it is time to educate them better to make better informed decisions about their security.

Agree: 1
Disagree
Informative
Unhelpful
Funny
Avatar

Jon Dillabaugh

Pro Focus LLC
In reply to Michael Henderson | 07/12/16 06:36pm

While I agree in general with your sentiments, I would like to know which brands are exempt from exploits, in your opinion?

Agree
Disagree
Informative
Unhelpful: 1
Funny

Marty Calhoun

IPVMU Certified | In reply to Michael Henderson | 04/08/17 03:39am

So when you refer to 'low end crap', do you mean that higher price = cyber secure? 

Agree
Disagree
Informative
Unhelpful
Funny

Michael Henderson

07/12/16 05:47pm

It isn't the brands, per se, but how the systems are designed. Working with the customers' IT people can limit exploits, dedicated security networks. Or for the safest route, a system that is not connected to the internet, except in cases of service and maintenance.

However, using shells that anyone can write a GUI for can lead to exploits from outside sources, due to not maintaining a standard of care for securing the code.

Staying with companies whose software is vetted to limit potential exploits is part of the due diligence integrators must look at when selecting a VMS.

Agree
Disagree
Informative
Unhelpful: 1
Funny
Avatar

Jon Dillabaugh

Pro Focus LLC
In reply to Michael Henderson | 07/12/16 07:02pm

Can you help me identify "companies who's software is vetted to limit potential exploits" vs ones who don't?

Agree: 1
Disagree
Informative
Unhelpful
Funny

Michael Henderson

In reply to Jon Dillabaugh | 07/12/16 08:32pm

Over the years, I and my co-workers have done that due diligence. I have systems I like, and systems I do not. But sharing that information is something I keep in house and treat as a intellectual property,.

Agree: 1
Disagree
Informative
Unhelpful: 3
Funny: 1
Avatar

Jon Dillabaugh

Pro Focus LLC
In reply to Michael Henderson | 07/12/16 09:04pm

Thanks! :)

I needed a good laugh today!

Agree: 2
Disagree
Informative
Unhelpful: 4
Funny

Michael Henderson

In reply to Jon Dillabaugh | 07/12/16 09:07pm

Whatever dude. Carry on with your systems, and I will do the same with mine.

Agree
Disagree
Informative
Unhelpful
Funny

Marty Calhoun

IPVMU Certified | In reply to Jon Dillabaugh | 04/08/17 03:42am

Thank you Jon, you hit the nail on the head for sure! Comments like those are what leads to all of the "mis-information" we deal with.

Agree: 1
Disagree
Informative
Unhelpful: 1
Funny
Avatar

Brian Karas

IPVM | 04/07/17 06:35pm

There is a new botnet being reported, called "Tsunami", that looks to be targeting the TVT devices. So far ~227,000 vulnerable devices have been identified:

New IoT/Linux Malware Targets DVRs, Forms Botnet

Agree
Disagree
Informative: 1
Unhelpful
Funny
Read this IPVM report for free.

This article is part of IPVM's 7,030 reports, 935 tests and is only available to members. To get a one-time preview of our work, enter your work email to access the full article.

Already a member? Login here | Join now
Loading Related Reports