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.

Database Security
Authentication
Mobile
Privacy
Compliance
Careers and People
Identity & Access Management
Security Monitoring
Advanced Threats
Insider Threats
Vulnerability Management
Comments
Nest Hack Leaves Homeowner Sleepless in Chicago
Newest First  |  Oldest First  |  Threaded View
WarnR
50%
50%
WarnR,
 User Rank: Apprentice
2/5/2019 | 10:07:15 AM
Troubling Comments
Tho I agree the home owner should and does bare some reasonability on this issue, I do find the comments troubling. Customers, like any user in a company, relies on the Computer & Security experts to guide them. If a user in a company is not trained about not sharing passwords, or leaving a computer unlocked due to no training, is it the user's fault or the Training team for not having the mandatory training?

A few questions come to my mind reading this - was the home owner informed that they information had become compromised? That they needed to change their passwords? Is there updated announcements regarding training of new features? Do users understand or even know that systems are not 100% secure no matter what?

The comments I had read have a touch of arrogance. Being in the computer and security field we understand these things. Not all users do. If you go to a Doc for a health issue, should the doc talk down to you or make comments about how you should have known something?  
blodgettcalvin
50%
50%
blodgettcalvin,
 User Rank: Apprentice
2/4/2019 | 11:24:26 AM
Not secure
This situation once again shows that modern technologies, such as the Internet of Things, do not fully provide people with complete safety
mattsweet
50%
50%
mattsweet,
 User Rank: Strategist
2/4/2019 | 10:39:31 AM
Subject needs to be changed
This was not a hack of Nest. This was typical enduser behavior. Google should have stated while they sympathize with the user, the user needs to be better educated to the harsh reality IoT can be and how to be responsible.

I do feel for the homeowners, though. I would be freaked out myself.
RyanSepe
0%
100%
RyanSepe,
 User Rank: Ninja
2/4/2019 | 9:16:12 AM
Re: Very misleading title
I concur with @hhendrickson274 assessment. The fault lies with the user. I also find it interesting that even though Google did nothing wrong, they had to take the PC route with that statement. It baffles me that even in a scenario like this, a titan like Google needs to release a statement such as to try to save face from the court of public opinion. 
ameerz
50%
50%
ameerz,
 User Rank: Apprentice
2/4/2019 | 7:07:19 AM
Re: Very misleading title
is this just a fad article??

what supporting views r shared??
hhendrickson274
100%
0%
hhendrickson274,
 User Rank: Strategist
2/3/2019 | 4:08:02 PM
Very misleading title
This was not a hack of Nest at all. This was user stupidity by refusing passwords across sites/services. I especially like how the user feels it is Googles fault and they should get their money back. Please change the title, unless you meant it to be click-bait. What happened is a very real consequence of users not taking their part in information security seriously, but it was not a hack based on the limited information presented in the article. This sort of sensationalism doesn’t serve to improve the state of affairs, it just perpetuates FUD.


Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
How Enterprises are Attacking the Cybersecurity Problem
Concerns over supply chain vulnerabilities and attack visibility drove some significant changes in enterprise cybersecurity strategies over the past year. Dark Reading's 2021 Strategic Security Survey showed that many organizations are staying the course regarding the use of a mix of attack prevention and threat detection technologies and practices for dealing with cyber threats.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-41154
PUBLISHED: 2021-10-18
Tuleap is a Free & Open Source Suite to improve management of software developments and collaboration. In affected versions an attacker with read access to a "SVN core" repository could execute arbitrary SQL queries. The following versions contain the fix: Tuleap Community Edition 11.1...
CVE-2021-41155
PUBLISHED: 2021-10-18
Tuleap is a Free & Open Source Suite to improve management of software developments and collaboration. In affected versions Tuleap does not sanitize properly user inputs when constructing the SQL query to browse and search revisions in the CVS repositories. The following versions contain the fix...
CVE-2021-41152
PUBLISHED: 2021-10-18
OpenOlat is a web-based e-learning platform for teaching, learning, assessment and communication, an LMS, a learning management system. In affected versions by manipulating the HTTP request an attacker can modify the path of a requested file download in the folder component to point to anywhere on t...
CVE-2021-41153
PUBLISHED: 2021-10-18
The evm crate is a pure Rust implementation of Ethereum Virtual Machine. In `evm` crate `< 0.31.0`, `JUMPI` opcode's condition is checked after the destination validity check. However, according to Geth and OpenEthereum, the condition check should happen before the destination validity check. Thi...
CVE-2021-41156
PUBLISHED: 2021-10-18
anuko/timetracker is an, open source time tracking system. In affected versions Time Tracker uses browser_today hidden control on a few pages to collect the today's date from user browsers. Because of not checking this parameter for sanity in versions prior to 1.19.30.5601, it was possible to craft ...