# Response to the 3/29/22 Security Report

**URL:** <https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865>\
**Category:** Wyze News\
**Tags:** important\
**Created:** [March 31, 2022, 10:08pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865 "2022-03-31T22:08:58Z")\
**Posts on this page:** 20\
**Page:** 5

<div class="post-metadata">

**Author:** ![Customer](https://avatars.discourse-cdn.com/v4/letter/c/e19b73/32.png) [@Customer](https://forums.wyze.com/u/Customer)\
**Post date:** [April 2, 2022, 8:42pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/82 "2022-04-02T20:42:25Z")

</div>

If you want off grid then the V2 using 3rd party Dafang firmware still sounds like the best bet, from what I have heard anyway.

---

<div class="post-metadata">

**Author:** ![MrWidget](https://avatars.discourse-cdn.com/v4/letter/m/7feea3/32.png) [@MrWidget](https://forums.wyze.com/u/MrWidget)\
**Post date:** [April 2, 2022, 10:17pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/83 "2022-04-02T22:17:43Z")

</div>

> not really something to worry about.  
> It speaks to an immature process.

> moderately clear  
> Any firmware, especially IoT firmware, that is not kept up to date is useless. Why waste the time to do it? Again, speaks to process. If it was done correctly, the build process would be such that anything that can be built once can be built again, on demand. Again, speaks to process.

I do firmware professionally for a living, and have for a long time, for companies large and small. IMHO, three years to patch a vulnerability, and half-baking a version of RTSP firmware probably means it hasn’t been integrated into any kind of build process, nor has it gone through any kind of formal validation. Which means you can’t trust it. If you can’t trust it, you shouldn’t run it. So far, Wyze has not commented, so we have nothing to go on.

---

<div class="post-metadata">

**Author:** ![peepeep](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/peepeep/32/107148_2.png) [@peepeep](https://forums.wyze.com/u/peepeep)\
**Post date:** [April 3, 2022, 7:03pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/84 "2022-04-03T19:03:08Z")

</div>

> [@Productive concern. Informed complaint](https://forums.wyze.com/t/productive-concern-informed-complaint/224194):
>
> Aim for it. &nbsp; clap &nbsp; clap[[The Wyze Cam Vulnerability and How the Verge Blew it Out of Proportion] ](https://www.youtube.com/watch?v=GdIQ5KrsWo0)

&nbsp;&nbsp;

---

<div class="post-metadata">

**Author:** ![chillycat](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/chillycat/32/9359_2.png) [@chillycat](https://forums.wyze.com/u/chillycat)\
**Post date:** [April 3, 2022, 7:49pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/85 "2022-04-03T19:49:43Z")

</div>

Well done !!!

………some will get it,

Others……………. not so much

---

<div class="post-metadata">

**Author:** ![Numps](https://avatars.discourse-cdn.com/v4/letter/n/d26b3c/32.png) [@Numps](https://forums.wyze.com/u/Numps)\
**Post date:** [April 3, 2022, 8:09pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/86 "2022-04-03T20:09:25Z")

</div>

A lot of opinions in this thread, most backed with few facts. Even The Verge which started this public commotion has quietly changed its story and admits it blew things out of proportion. The threat is low. The primary problem is the time taken to admit the problem…in part because a pandemic slowed development of solutions. It’s always best not to point out the problem until you have a fix, and that’s what Wyze did.

---

<div class="post-metadata">

**Author:** ![JCR](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/jcr/32/49055_2.png) [@JCR](https://forums.wyze.com/u/JCR)\
**Post date:** [April 4, 2022, 3:09am UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/87 "2022-04-04T03:09:33Z")

</div>

I am sorry, nope. Lack of resources is not, never will be, an excuse.

Actually being clean and open about vulnerabilities and how to mitigate in the absence of a fix would have been the correct policy.

It is rather unfortunate for Wyze, this was their choice. This would’ve been the worst case outcome when they evaluated the situation this 3 yrs ago , In fact, I hope they are rational enough to have considered this outcome.

I now have probably over US $1k invested in Wyze products. I also have a rather large amount of discretionary income, that as a geek, I like to spend on tech. Wyze has a market advantage on value.  
But I _currently_ have lost trust in Wyze’s execution. It will take a considerable amount of work on their part to make me trust them enough to continue supporting (buying) their video/audio products.

I am disappointed.

---

<div class="post-metadata">

**Author:** ![towelkingdom](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/towelkingdom/32/107247_2.png) [@towelkingdom](https://forums.wyze.com/u/towelkingdom)\
**Post date:** [April 4, 2022, 3:17am UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/88 "2022-04-04T03:17:31Z")

</div>

Honestly, wyze definitely shouldn’t have made it known until it was fixed. Regardless how big or small the issue was. That’s like giving a step by step guide to criminals on how to break into your house.

---

<div class="post-metadata">

**Author:** ![FullOfBeans](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/fullofbeans/32/57726_2.png) [@FullOfBeans](https://forums.wyze.com/u/FullOfBeans)\
**Post date:** [April 4, 2022, 4:04am UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/89 "2022-04-04T04:04:24Z")

</div>

Agreed, although it’s unimaginable that it would take three years to issue a fix. And the white paper published by Bitdefender gave that exact blueprint to potential miscreants. And has Wyze notified ALL cam owners with the details about it even yet?

---

<div class="post-metadata">

**Author:** ![towelkingdom](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/towelkingdom/32/107247_2.png) [@towelkingdom](https://forums.wyze.com/u/towelkingdom)\
**Post date:** [April 4, 2022, 4:13pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/92 "2022-04-04T16:13:04Z")

</div>

I find it mildly amusing that SEVERAL users have wanted a way to access their cameras SD recordings over their home network… And apparently that was possible, but no one knew how to do it. The very thing that people have wanted is now being called a vulnerability and was patched.

---

<div class="post-metadata">

**Author:** ![FullOfBeans](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/fullofbeans/32/57726_2.png) [@FullOfBeans](https://forums.wyze.com/u/FullOfBeans)\
**Post date:** [April 4, 2022, 4:17pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/93 "2022-04-04T16:17:08Z")

</div>

So those users should be delighted to scarf up all the v1s people have said they are trashing.

This long episode clearly indicates that Wyze does not want to provide customers with a legit way to access their cam’s sd card files remotely. I wonder why. 🤔

---

<div class="post-metadata">

**Author:** ![towelkingdom](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/towelkingdom/32/107247_2.png) [@towelkingdom](https://forums.wyze.com/u/towelkingdom)\
**Post date:** [April 4, 2022, 4:40pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/94 "2022-04-04T16:40:24Z")

</div>

I don’t think that’s the case, since it was possible, but when some third party came in and said it’s a vulnerability and not a feature…

I wish wyze would have just, I dunno, researched how to make it a feature rather than patch a ‘bug’.

---

<div class="post-metadata">

**Author:** ![FullOfBeans](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/fullofbeans/32/57726_2.png) [@FullOfBeans](https://forums.wyze.com/u/FullOfBeans)\
**Post date:** [April 4, 2022, 4:53pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/95 "2022-04-04T16:53:09Z")

</div>

Agreed. That’s why I assume Wyze doesn’t want that capability to be available to customers. Wyze had three years to implement a “safe” / company approved way for customers to satisfy their desire to access their SD cards remotely but chose not to.

So whether it’s a bug or a feature depended on Wyze’s reaction to its discovery by a third party. Wyze chose to treat it as a bug despite the opportunity it provided for Wyze to engineer it into being a feature.

---

<div class="post-metadata">

**Author:** ![curtistmiller](https://avatars.discourse-cdn.com/v4/letter/c/e36b37/32.png) [@curtistmiller](https://forums.wyze.com/u/curtistmiller)\
**Post date:** [April 5, 2022, 3:37pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/96 "2022-04-05T15:37:07Z")

</div>

Perfect message. Note the response you received, none. They care more about promoting their life then running a business it appears.

---

<div class="post-metadata">

**Author:** ![FullOfBeans](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/fullofbeans/32/57726_2.png) [@FullOfBeans](https://forums.wyze.com/u/FullOfBeans)\
**Post date:** [April 5, 2022, 3:48pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/97 "2022-04-05T15:48:02Z")

</div>

I agree that this really nails the salient issues that remain unaddressed and will continue to bedevil both customers and Wyze until they take the appropriate measures necessary to turn their cheap flowery assurances into action that demonstrates sincerity and trustworthiness.

> [@Response to the 3/29/22 Security Report](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/36):
>
> @WyzeGwendolyn - mostly just tagging you to make sure this is read. As a software engineer myself, I understand the limitations in the v1 cam and that any patching takes time. I also understand the local access limitations, and how ‘access to internal network traffic’ is a barrier to easy exploitation. However, there are failures here that I think Wyze will need to demonstrate that they will learn from: Disclosure timeframe - We would all love to say patches should be ready within minutes an…

---

<div class="post-metadata">

**Author:** ![raygam](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/raygam/32/56797_2.png) [@raygam](https://forums.wyze.com/u/raygam)\
**Post date:** [April 5, 2022, 3:59pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/98 "2022-04-05T15:59:39Z")

</div>

> [@curtistmiller](#):
>
> Perfect message. Note the response you received, none. They care more about promoting their life then running a business it appears.

Indeed! While many seem hung up on the severity of the issues or the validity of the Verge article, your post is exactly the point - the time it took to acknowledge and the response (or lack thereof) to the reported issue. Successful companies have been created in less than 3 years!

Cheers!

---

<div class="post-metadata">

**Author:** ![peepeep](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/peepeep/32/107148_2.png) [@peepeep](https://forums.wyze.com/u/peepeep)\
**Post date:** [April 5, 2022, 4:04pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/99 "2022-04-05T16:04:29Z")

</div>

C’mon, kids, this is 2022. This ain’t over 'til there’s groveling. 😉

---

<div class="post-metadata">

**Author:** ![FullOfBeans](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/fullofbeans/32/57726_2.png) [@FullOfBeans](https://forums.wyze.com/u/FullOfBeans)\
**Post date:** [April 5, 2022, 4:25pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/100 "2022-04-05T16:25:16Z")

</div>

And it might just be that it’s taken these three years for Wyze’s own actions to destroy it.

The severity of the risk is irrelevant. There’s always gonna be risk of some nature with technology. What matters is how proactively a company communicates and responds that can make or break how confident customers feel about them.

I have money to spend on additional smart home products, but all plans are on hold for now and will ultimately be diverted to other companies unless Wyze makes a course correction in the way it deals with this issue going forward.

It seems like I’m not alone in those feelings, considering the numbers of others who have expressed their disgust.

Is this the hill that Wyze is willing to die on? If so, it’s sad and unfortunate.

---

<div class="post-metadata">

**Author:** ![peepeep](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/peepeep/32/107148_2.png) [@peepeep](https://forums.wyze.com/u/peepeep)\
**Post date:** [April 5, 2022, 4:28pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/101 "2022-04-05T16:28:43Z")

</div>

Tone and tenor. Tone trumps tenor every time. Sadly.

> [@UPDATE YOUR FIRMWARE - Wyze Cam flaw lets hackers remotely access your saved videos ( \* if they can gain access to your local network/WiFi )](https://forums.wyze.com/t/update-your-firmware-wyze-cam-flaw-lets-hackers-remotely-access-your-saved-videos-if-they-can-gain-access-to-your-local-network-wifi/223550/94):
>
> > [@UPDATE YOUR FIRMWARE - Wyze Cam flaw lets hackers remotely access your saved videos ( \* if they can gain access to your local network/WiFi )](https://forums.wyze.com/t/update-your-firmware-wyze-cam-flaw-lets-hackers-remotely-access-your-saved-videos-if-they-can-gain-access-to-your-local-network-wifi/223550/87):
> >
> > “We are taking privacy extremely seriously” isn’t an answer, it’s a PR statement.
> 
> What if it’s true? Should they avoid saying it to avoid triggering customers’ PR skepticism? 😉

---

<div class="post-metadata">

**Author:** ![FullOfBeans](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/fullofbeans/32/57726_2.png) [@FullOfBeans](https://forums.wyze.com/u/FullOfBeans)\
**Post date:** [April 5, 2022, 4:52pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/102 "2022-04-05T16:52:47Z")

</div>

Not even that. It’s a matter of action vs inaction. Wyze STILL has not reached out directly to cam customers to give them a straightforward explanation of the specifics unadorned by excuses and marketing platitudes, i.e., what customers should be concerned about and how to avoid it. Specifics. Not generalities and vagaries.

Why haven’t they? Is it because they can’t without occurring a whole lot more questions? If so, so be it. The level of the company’s maturity is demonstrated by how it responds in the face of its own customer’s questions.

Simply posting a statement on the forum will reach comparatively few customers and many of those are the most diehard loyalists who will continue to support the company regardless because they need the company to survive in order to continue to receive support for their investments both material and emotional. But Wyze can’t live by old customers alone. It needs a constant flow of new capital, new customers and ongoing sales.

New and potential customers will probably demand more in order to build confidence coming out of this situation.

---

<div class="post-metadata">

**Author:** ![chillycat](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/chillycat/32/9359_2.png) [@chillycat](https://forums.wyze.com/u/chillycat)\
**Post date:** [April 5, 2022, 4:59pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/103 "2022-04-05T16:59:04Z")

</div>

And there should be NO groveling ………NOT EVEN A HINT

[Previous page](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865.md?page=4)

[Next page](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865.md?page=6)
