Response to the 3/29/22 Security Report

They’re afraid. Of the agitated .0001 of their customer base…

… .01 of which are trained ‘vocalists.’ :wink:  

2 Likes

Here it comes…….”on deck circle”

And being dismissive is the most effective way of exacerbating and prolonging a disagreement. And it solves/changes nothing for the better.

Anyone who’s ever been married has had plenty of opportunity to learn that lesson.

As the Community Guidelines directs, address the content of the argument rather than personally attack or degrade the poster(s).

Nothing worthwhile to add? Shrug… I shall miss your posts.
Don’t bother to reply as I will not see it. Bye.

2 Likes

Feigning boredom with a thread while voluntarily pouring over every post day after day:

image

1 Like

That’s about as substantive a point as I can make.

I welcome your informed dissent. :slight_smile:

1 Like

To borrow your terminology, then, there appear to be “trained vocalists” on both sides of the debate. So what’s the point you are trying to make. Please educate me.

We disagree. I doubt either of us will be winning the other over today.

Anyone interested can go back through the active threads on this topic to see how the debate evolved.

That will likely comprise less than one person (because ‘multitasking.’) :slight_smile:

There are more than two binary sides in regard to this matter. I have never been of a mind that the degree of the risk was the primary issue.

I am exclusively concerned about Wyze’s transparency and responsiveness. There was and still is a way and need for Wyze to fully inform and educate its customers about this and any other security related issue going forward and i am not alone in my reservations over whether Wyze has demonstrated that there will not be a similar if not worse failure to communicate looming in the unsuspecting future that I am not anxious to experience.

If you are content with the way it was handled, then you have no complaints and good for you. Really. Also, then it would bode well to ignore those who do if you can’t or don’t care to address those concerns in a direct, sincere (non-snarky) and constructive (non-personal) way. But it’s not constructive to diminish the character or direct passive-aggressive swipes at those who have remaining doubts and concerns. Unless, that is, you intend to heighten the temperature, insult or otherwise bugger others which is the opposite of respectfully agreeing to disagree.

1 Like

peep, of course not. The entirety of the statement is okay, sort of. It is still defensive and still claiming that what they did was okay. It is not.
Visit their website right now. Any banner or link to the response on the home page? That’s a pretty standard responsible action you’ll see companies do. Did they send out emails? I never received one, and there’s no lack of them sending emails trying to sell me things like pretty flashing lights and monthly security system (yeah, sure, almost had me there)
There are two things most of us have. A disaster recovery (DR) policy and a Security incident response policy. You write them and review them periodically. You hope you never have to open them except for review. They aren’t studied or memorized. They are very much like the emergency checklist you’ll see a first officer on a flight pull out when there is an issue. You go line by line. Because the initial impact rating for this is low, it doesn’t mean you close the book and put it away. It means you finish the list according to that impact. Somewhere in that list is “notify users” and it isn’t three years later.

4 Likes

As an aside… has anyone here contacted Wyze support with any questions lately? Either email or through the app seems to make but little difference. Their response, including the mea culpas, take some 10-15 days average time.

As a retired Director of IT whose responsibility once included a sizeable help desk as well, I can say that the support group would have had a major overhaul if they responded at that rate. That too is indicative of something. I have no real stake in any of this as I purchased only a single camera to test with all other purchases on hold. Not my circus, not my monkeys. Yet, the Wyze response - or lack thereof - suggests something.

I don’t really have much else to add so, have a great week, everyone!

Cheers!

2 Likes

Bingo.

Neither is it advisable for pilots, in a similar situation after an emergency has passed, to call back to the alarmed passengers in the cabin to say something to the effect of, “Why all the drama and over-reaction? It seemed worse than it was. Now let’s all stop talking about it and STFU, you bunch of ‘professional complainers’”

I used to run a customer service help desk as well.

Aside from the constant obsequious apologies of the Wyze support agents as part of their script, and maybe including even that too when it doesn’t accompany a solution, there’s nothing about that level of unresponsiveness that is okay.

1 Like

FWIW, I too have been an early loyal Wyze customer, and a lurker on the forums. I am very disturbed over the three-year delay in acknowledging this problem. It’s hard to reconcile this complete disregard for security with the glossy security marketing that Wyze pushes daily. Wyze will have to work to win back my trust.
Once people digest what has happened, Wyze’s public reputation will suffer. Unfortunately, the rot seems to be at the top management. Why no whistleblowers?

https://9to5mac.com/2022/03/31/wyze-cam-security-flaw/

1 Like

Their pathetic attempt to state, “they actually notified individuals is pathetic.” I have used WYZE for over 2 years and have loved their products…However this was a huge step back in the wrong direction. It would seem INTEGRITY has little to do with their business decisions or company values. It is not hard to come out and say what we found from a security standpoint and still protect their business…

Its not like ppl are dumb.

A summation: “They crafted a well-worded email stating EOL of a product but neglected to disclose their findings as they were afraid it would hurt their pocket books and didn’t want to lose money…”

Shrewd and uncivilized. I will give them grace for a second attempt but wish they would at least fess up to doing wrong and swallow their pride. That would probably save them the most money as it stands if that is their business goal.

All-in-all, its a shame. Gonna put a freeze on purchasing products from them for a bit till hopefully the release a better apology.

2 Likes

More voices heard from (courtesy TWiT Tech Podcast).

“Vulnerable is vulnerable…to not even let people know…, hey, this is a security device which you are selling as a security device that is capturing pretty sensitive information, has vulnerabilities where people could take it over and could do things to it AND YOU’RE NOT TELLING ANYONE…That’s not acceptable at all and I think we should hold their feet to the fire.”

Well, there’s a bit too much sensationalism in there as well. I thought I was listening to a certain “news” station on either side of the fence.
One thought is how many people will now get blackmail emails from people saying you know, we hacked your camera and you were doing bad things. I get them all the time about hacking my webcam - on an email account at work that doesn’t have a webcam.
The truth is that for the average user, they really weren’t vulnerable. As others and myself have said, if you have someone with access behind your router/firewall, you have more problems than worrying about them looking at a probably boring cam.

But, the lack of notification over a 3yr period is not forgivable. I don’t think they focused on it nor even tried to fix it. I’d have offered to replace them if you couldn’t fix them. To date, have the users been notified?

5 Likes

I don’t disagree with you at all. And No, I don’t think anyone has been notified in the way you mean.

So I posted that video to point out another example of what’s being said outside of this (mostly) echo chamber that is going unopposed by any definitive statement by Wyze made directly to customers that meets this head on.

And Wyze’s silence is deafening.

Even if forum members are content to let it fade into obscurity, there’s a big world out there full of customers, and would-be customers who aren’t on this forum and won’t hear both sides of the story. Wyze has an opportunity to turn the narrative around if they meet this challenge bravely and honestly. But they are letting it slip away.

I’d bet every tech/security related podcast and YouTube channel would jump at the chance to interview a Wyze representative.

1 Like

@mike21 you’re a pleasure to read. :slight_smile:

2 Likes

I will just add an echo to the main theme of this thread. For me its not the vulnerability itself that I have issue with its the lack of transparency from Wyze.
My guess is that they kept it quiet because they were trying to secure financing to keep the lights on and any bad press at the time (wether from within or outside) would have made securing that financing even harder.
The problem I see is this…if they’ve done it before…what is stopping them from doing it again? Who’s to say there isn’t another, more crictical, vulnerability that currently plagues their products the whole while they entire customer base is blissfully unaware.

2 Likes