Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Vulnerabilities / Threats

Webcam Bug Enables Virtual Home Invasions

Trendnet releases firmware updates to prevent home security cameras from being accessed without a password.

A webcam vulnerability has left users at risk of having their video feeds viewed by anyone with an Internet connection.

In particular, the firmware for 22 webcam models sold by Trendnet since April 2010 has a bug that allows anonymous connections to be made to the cameras, without requiring a password. According to a statement published on the company's website earlier this week, "Trendnet's security team understands that video from some Trendnet IP SecurView cameras may be accessed online in real time. Upon awareness of the issue, Trendnet initiated immediate actions to correct and publish updated firmware which resolves the vulnerability."

Tuesday, the company had patched only seven webcam models, reported the BBC. But by Thursday, Trendnet said that it had released updated firmware--fixing the vulnerability--for all 22 of the affected webcams. The company estimates that approximately 50,000 of its devices, which are sold both inside and outside the United States, are affected by the vulnerability. The company has added an alert about the firmware update to its website, and said it plans to notify the 5% of affected users who registered their webcams with the company after purchase.

[ Buying on the black market gets cheaper. See 'Factory Outlets' Sell Stolen Facebook, Twitter Credentials. ]

A Trendnet official blamed the bug on a "coding oversight." But the company has yet to issue any other types of statements to alert its customers. "We are planning an official release of information to the public concerning this, but in advance I can tell you that this week we are targeting to have firmware to all affected models," Zak Wood, Trendnet's director of global marketing, told the BBC earlier this week.

Some customers may question the delay between knowledge of the vulnerability becoming public--one month ago--and Trendnet issuing fixes. Specifically, on January 10, someone posting under the handle "someluser" on the Console Cowboys blog reported finding that while the Trendnet TV-IP110w--SecurView Wireless Internet Camera--he tested could be configured to require passwords, it would also accept anonymous requests. Taking what he learned, he was able to query Shodan--a search engine that can locate specific types of Internet-connected devices, including their IP addresses--and find at least 350 vulnerable devices. All of the cameras could apparently be accessed by appending the same 15-character code snippet to the camera's IP address.

That finding was picked up last week by the Verge, which reported that following the Console Cowboys post, "links to the compromised feeds spread quickly on message boards like Reddit and 4chan," while Pastebin posts released shortly thereafter listed links to what they said were 1,000 accessible webcams. Those links reportedly resolved to everything from children's rooms and cat beds to parking lots and office doors.

The Trendnet research echoes a recent study conducted by HD Moore, who found that numerous videoconferencing systems are misconfigured and poorly secured, which gives attackers the ability to eavesdrop on sensitive communications.

The right forensic tools in the right hands are just a start. The new Digital Detectives issue of Dark Reading shows you how to better apply the lessons they teach. (Free registration required.)

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Mathew
50%
50%
Mathew,
User Rank: Apprentice
2/10/2012 | 4:21:30 PM
re: Webcam Bug Enables Virtual Home Invasions
DibbleDabble, thanks very much for the additional details. Yes, while the vulnerability appears to have been around since 2010, it was apparently just noticed/publicized. Good to know that not everyone's potentially affected Trendnet webcam will be set to port 80 as well. Though as the endless lists of IP addresses circulating on Pastebin and file-sharing demonstrate, many owners apparently do have theirs set to port 80.
In addition, while it would be a technical challenge, theoretically it wouldn't be too difficult to write a script that would crawl Shodan, then begin testing port numbers to attempt to gain access to camera streams that weren't set to port 80. Not saying that anyone is doing this, but some "unauthorized snoopers" may have time to kill.
What's going to be difficult, however, is getting updates to people who don't know they should update.
Best regards,
Mathew Schwartz
DibbleDabble
50%
50%
DibbleDabble,
User Rank: Apprentice
2/9/2012 | 11:38:06 PM
re: Webcam Bug Enables Virtual Home Invasions
Great article, but I would like to add a little updated info I received today.

At first I was pretty upset to find that my living room IP camera had been freely broadcasting live video to any willing Internet onlooker. So I went to Trendnet for more answers, and after further investigation I found that gaining access was more difficult than one would expect.

In order to gain access using only the IP address [ex. 123.123.123.123/anony/mjpg.cgi], the camera would need to be configured for port 80. Luckily my camera was set to a different value making access to my web camera more difficult. I learned that the unauthorized viewer/user would need to add port information to view my camera stream [ex. 123.123.123.123:##/anony/mjpg.cgi] the numbers after the colon represent the unique port number to access the camera's stream. Knowing this piece of info alone alleviated much of my fears of unauthorized snoopers peering into my personal life.

Lastly, I found that this camera vulnerability is actually NEW?!? When I read all of the articles about this issue, they refer to a date in 2010 when this vulnerability showed up in the camera's firmware. Actually this somewhat true. What I found was the bug in the firmware has been there since 2010, but only recently has that bug or piece of code been exploited to gain access to video stream. Meaning unauthorized access has only been available for the last few weeks since the announcement by console cowboys.
COVID-19: Latest Security News & Commentary
Dark Reading Staff 9/25/2020
Hacking Yourself: Marie Moe and Pacemaker Security
Gary McGraw Ph.D., Co-founder Berryville Institute of Machine Learning,  9/21/2020
Startup Aims to Map and Track All the IT and Security Things
Kelly Jackson Higgins, Executive Editor at Dark Reading,  9/22/2020
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Special Report: Computing's New Normal
This special report examines how IT security organizations have adapted to the "new normal" of computing and what the long-term effects will be. Read it and get a unique set of perspectives on issues ranging from new threats & vulnerabilities as a result of remote working to how enterprise security strategy will be affected long term.
Flash Poll
How IT Security Organizations are Attacking the Cybersecurity Problem
How IT Security Organizations are Attacking the Cybersecurity Problem
The COVID-19 pandemic turned the world -- and enterprise computing -- on end. Here's a look at how cybersecurity teams are retrenching their defense strategies, rebuilding their teams, and selecting new technologies to stop the oncoming rise of online attacks.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2020-15208
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, when determining the common dimension size of two tensors, TFLite uses a `DCHECK` which is no-op outside of debug compilation modes. Since the function always returns the dimension of the first tensor, malicious attackers can ...
CVE-2020-15209
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, a crafted TFLite model can force a node to have as input a tensor backed by a `nullptr` buffer. This can be achieved by changing a buffer index in the flatbuffer serialization to convert a read-only tensor to a read-write one....
CVE-2020-15210
PUBLISHED: 2020-09-25
In tensorflow-lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, if a TFLite saved model uses the same tensor as both input and output of an operator, then, depending on the operator, we can observe a segmentation fault or just memory corruption. We have patched the issue in d58c96946b and ...
CVE-2020-15211
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 1.15.4, 2.0.3, 2.1.2, 2.2.1 and 2.3.1, saved models in the flatbuffer format use a double indexing scheme: a model has a set of subgraphs, each subgraph has a set of operators and each operator has a set of input/output tensors. The flatbuffer format uses indices f...
CVE-2020-15212
PUBLISHED: 2020-09-25
In TensorFlow Lite before versions 2.2.1 and 2.3.1, models using segment sum can trigger writes outside of bounds of heap allocated buffers by inserting negative elements in the segment ids tensor. Users having access to `segment_ids_data` can alter `output_index` and then write to outside of `outpu...