Slashdot Mirror
IZON IP Cameras Riddled With Security Flaws
An anonymous reader writes "With recent action by the FTC against TRENDnet, the 'Internet of Things' has taken a sharp turn in the eyes of the public and government with regard to security. This week, Duo Security employee Mark Stanislav presented security research he did on the IZON IP camera from Stem Innovation. Through his testing, Mark found hardcoded credentials for Linux accounts (accessible by Telnet; Yes, — really), an undocumented web interface allowing for viewing a camera's stream (also with hardcoded credentials, user/user), and a variety of other failings including a lack of cryptography in most of the camera's functionality, including when uploading videos to Amazon Web Services's S3 storage." According to the above-linked article, "Contacted by The Security Ledger, Stem Innovation CTO Matt McBeth said that the IZON firmware, server system and iOS applications tested by Stanislav have since been updated, and that the research contains “inaccurate and misleading information.” Stem did not provide specific information about any inaccuracies."
I'll be generous and guess that IZON farmed out too much of their software development to ... wherever. Perhaps the company's principals are more hardware oriented, but it's interesting that they're now advertising for an iOS team lead.
Luke, help me take this mask off
...so do a lot of things - who gives a shit!
People that like to be able to watch what goes on inside their homes when they're gone, but don't want every spook and perv on the planet to be able to as well?
Do we really need a new story for each one of these?
How else would you know about it?
Man, it seems the trolls are running out of material these days.
An enigma, wrapped in a riddle, shrouded in bacon and cheese
Here's what happens... The company gets a Linux SDK from some chip vendor which works on some reference platform. This is intended for development and evaluation purposes and has many interfaces exposed, which is generally what you want for development. The producer then hires some cheap amateurish programmers to write some application code on top of the SDK to make the product do stuff. The stock kernel and filesystem is deployed as-is. No security audit is done, no unnecessary services are closed, and few things are removed from the stock SDK filesystem. It will never get fixed for any or all of the following reasons: 1) No one at the company has enough experience to lock down/strip down Linux - they just know how to write applications on-top. 2) There are deadlines and the management has a "it works, ship it!" mentality. 3) Some developer/engineer might know how to do things properly, but is so swamped with deadlines and babysitting all the juniors that it can't happen.
This is just a consumer-grade device, I'm more worried about actual supposedly "professional grade" security cameras. For example the IQInvison cameras all have the hard-coded username/password of root/system and YOU CAN'T CHANGE IT. Several cameras can only take 6-8 character lower case alpha-numeric passwords. Many of them have root or system as their only user. Only Axis and Pelco seem to have a clue that a security device should actually be secure.
"Think about how stupid the average person is. Now, realise that half of them are dumber than that." - George Carlin
A back door is not a security flaw. It's there by design not by accident.
A backdoor is a security flaw if
a) the owners are not told that it is there (or)
b) the owners can not turn it off (or)
c) if the FTC says it is.
There are (deliberately vague) promises about security made on the IZON site.
IZON lets you watch & listen from anywhere, with secure access to the IZON video stream.
To not reveal a backdoor account has already been found by the FTC (see first link) as a violation which
gets you 20 years worth of monitoring: Per the FTC in the TrendNet case:
The company also is required to obtain third-party assessments of its security programs every two years for the next 20 years.
Sig Battery depleted. Reverting to safe mode.
Until the really awfully managed company decided to outsource all of the software development to contractors. This was after wiping out the team in place before I joined. They are a very unstable company, which really favors knee-jerk decision making. I'm not surprised by any of this, the company is run by the idiot kid of a rich guy who doesn't know the first thing about tech. The hardware was well designed by the CTO, who apparently isn't able to steer the technology decisions of the company. Unfortunate. He's a good guy. But the company is ultimately helmed by the CEO, and he's a fat fucking moron.