# 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:** 3

<div class="post-metadata">

**Author:** ![jhoff](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/jhoff/32/57634_2.png) [@jhoff](https://forums.wyze.com/u/jhoff)\
**Post date:** [April 1, 2022, 7:33pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/42 "2022-04-01T19:33:45Z")

</div>

To me, people here that are equating this to something similar to someone giving them keys to your house so they can walk in on you in the shower are a bit out of bounds. Security vulnerabilities in IOT gear, or any connected tech for that matter, are going to happen. no doubt. You can look through reports and find vulnerabilities for basically every tech company out there. Some go unpatched forever.

My point is we need to focus on what we’re mad about here.

3 years is much too long to secretly hold onto the knowledge, definitely. Wyze **must** do better with that, because trust is hurt with this as people don’t know that when a new vulnerability is found that it will be addressed timely. In my view the correct response (since the v1 was EOL already) would have been to immediately release the info and advise to stop using v1. However, we as consumers also must understand that technology is not supported forever and at some point products stop being supported and we cannot assume that EOL products will ever be fixed. That’s not an obligation at that point.

IOT is inherently risky no matter what company you get products from. It’s a trade off for the accessibility/ease of use. It’s short-sighted to expect those products to be supported forever.

Last thing: To those talking referencing that you give out your wifi password to every visitor you have…please learn about guest networks. That way you can share your internet connection to everyone you see in the world but they don’t have immediate access to everything on your LAN. It’s still not great to do that but beats letting everyone on your LAN.

---

<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 1, 2022, 7:33pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/43 "2022-04-01T19:33:51Z")

</div>

> [@UserCustomerGwen](#):
>
> We know there’s discussion about the recent BitDefender report and we wanted to make sure that you all have access to our statement regarding the contents of this report.

Could there have been discussions about it because the original report dates back to March 2019 and your statement comes 3 bloody years later in 2022?! _ **Seriously lousy response** _ . . . just sayin’ . . .

---

<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 1, 2022, 7:42pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/44 "2022-04-01T19:42:45Z")

</div>

> [@jhoff](#):
>
> My point is we need to focus on what we’re mad about here.
> 
> 3 years is much too long to secretly hold onto the knowledge, definitely. Wyze **must** do better with that, because trust is hurt with this as people don’t know that when a new vulnerability is found that it will be addressed timely.

Exactly!

---

<div class="post-metadata">

**Author:** ![cgeorgia09](https://avatars.discourse-cdn.com/v4/letter/c/2bfe46/32.png) [@cgeorgia09](https://forums.wyze.com/u/cgeorgia09)\
**Post date:** [April 1, 2022, 7:54pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/45 "2022-04-01T19:54:22Z")

</div>

Spot on

---

<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 1, 2022, 7:56pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/46 "2022-04-01T19:56:47Z")

</div>

> [@towelkingdom](#):
>
> The vulnerability that was exposed was minor, to be frank. Someone would have to have already accessed your wifi. Unless you’re turned off and bypassed all the security measures on your router, you weren’t vulnerable to this type of hacking.

Perhaps the point is what many call transparency, not the graveness of the vulnerability. Having worked in numerous IT management functions (with some companies significantly larger and some smaller than Wyze) I know of few businesses which wait 3 years to talk about a security report. Folks are unhappy with the response, or lack thereof, more than the type of vulnerability.

---

<div class="post-metadata">

**Author:** ![Karel](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/karel/32/38695_2.png) [@Karel](https://forums.wyze.com/u/Karel)\
**Post date:** [April 1, 2022, 7:57pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/47 "2022-04-01T19:57:06Z")

</div>

Wow what a mess on the forum.  
If there is a network plug or WiFi, you have to take into account that hackers can get to it if they want to.  
I’ll be ordering a few more beautiful V3 models in the near future.  
Have a nice day.

---

<div class="post-metadata">

**Author:** ![cgeorgia09](https://avatars.discourse-cdn.com/v4/letter/c/2bfe46/32.png) [@cgeorgia09](https://forums.wyze.com/u/cgeorgia09)\
**Post date:** [April 1, 2022, 7:57pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/48 "2022-04-01T19:57:10Z")

</div>

Exactly. Security is an illusion. Their employees and system have back doors to allow tech support and flashing of firmware. My piss is about the lack of disclosure.

---

<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 1, 2022, 8:05pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/49 "2022-04-01T20:05:46Z")

</div>

> [@FullOfBeans](#):
>
> Not everyone lives in a robust 5G or even LTE location. In that case, allowing a visitor access to the LAN is humane.

I mostly agree with you, especially on the subject of Wyze’s irresponsible behaviour. However, the humane thing to do is to turn on what we used to call “guest network” at Cisco, long ago and far away … ::

---

<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 1, 2022, 8:31pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/50 "2022-04-01T20:31:33Z")

</div>

Messy indeed.

But I did get a WyzeLock **today** for 1/2 off. 😂

---

<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 1, 2022, 8:38pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/51 "2022-04-01T20:38:31Z")

</div>

Yep. I said that in a previous post myself. Thanks.

---

<div class="post-metadata">

**Author:** ![HoZr](https://avatars.discourse-cdn.com/v4/letter/h/ed8c4c/32.png) [@HoZr](https://forums.wyze.com/u/HoZr)\
**Post date:** [April 1, 2022, 8:59pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/52 "2022-04-01T20:59:18Z")

</div>

“ **We were transparent with our customers** and disclosed our inability to continue to offer necessary security updates **in an email** announcing the end-of-life (EOL) for this product. For security reasons, we again _chose to remain prudent about the specific reason why_ until now to limit the risk to all of our affected users across affected models. **We strongly suggest** that our customers no longer use EOL products as security and other critical updates are no longer provided, and **we continue to urge** Wyze Cam v1 owners to discontinue the use of these products.”

Which PR firm did you hire to wordsmith this? And how do you blame customers for not heeding your “vaguely worded emails?” Sounds like you’re blaming the victims here for not intuiting the actual danger you failed to convey.

Also, the part I’m not clear on is you say “only if they accessed your network”. How many IOT devices have allowed exactly this? Remote access to networks?

I’m sure it’s all hands on deck right now but @UserCustomerGwen please clarify the level of access required for camera access.

Thanks.

---

<div class="post-metadata">

**Author:** ![Known1](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/known1/32/32230_2.png) [@Known1](https://forums.wyze.com/u/Known1)\
**Post date:** [April 1, 2022, 9:20pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/53 "2022-04-01T21:20:14Z")

</div>

Since v2 came out about a year after the v1, should we expect the v2 to be EOL in about a year? Or is it more realistic to expect the v2 EOL announcement to occur about 2-3 months prior to the next round of vulnerability disclosures?

---

<div class="post-metadata">

**Author:** ![tbagcam](https://sea2.discourse-cdn.com/wyze/user_avatar/forums.wyze.com/tbagcam/32/107526_2.png) [@tbagcam](https://forums.wyze.com/u/tbagcam)\
**Post date:** [April 1, 2022, 9:20pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/54 "2022-04-01T21:20:17Z")

</div>

I’m annoyed with the 10 mins I wasted reading this drama.

If yur annoyed with Wyze, you’ll prolly also be annoyed with hundreds of companies, especially auto dealerships.

Furthermore, human behavior itself is monumentally more frustrating, if one were to objectively evaluate it.

---

<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 1, 2022, 11:25pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/55 "2022-04-01T23:25:41Z")

</div>

> [@tbagcam](#):
>
> Furthermore, human behavior itself is monumentally more frustrating,

Q.E.D.

---

<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 1, 2022, 11:34pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/56 "2022-04-01T23:34:51Z")

</div>

LOl @raygam. You said it better thsn I could’ve.

I’ve said it elsewhare and it bears including here:

There are effective ways of bringing an end to drama and lessen the controversy when a mistake is made.

 ![image](https://us1.discourse-cdn.com/wyze/original/3X/8/f/8f09b4654be068e81241b4342661909eeca5ef20.jpeg)

OR you can do what Wyze did and is continuing to do which is feeding the continued flap:

- Refuse to admit a mistake/betrayal of trust was made.

- Refuse to take responsibility for the mistake/betrayal of trust.

- Refuse to listen to and respond appropriately to those who express a feeling of betrayal of trust.

- Discuss the incident in a vague or evasive manner.

- Make Excuses and attempt to shift blame.

Please, Wyze. Just admit you should’ve done better, full stop without excuses. Announce your plan for how this kind of thing will be avoided in the future. And endeavor to Make amends.

---

<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 2, 2022, 12:53am UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/57 "2022-04-02T00:53:45Z")

</div>

its dead already

![439](https://us1.discourse-cdn.com/wyze/original/3X/0/a/0a8aea898aef6987b415568fcf2c1e2c545399d0.gif)

---

<div class="post-metadata">

**Author:** ![nbl](https://avatars.discourse-cdn.com/v4/letter/n/7c8e57/32.png) [@nbl](https://forums.wyze.com/u/nbl)\
**Post date:** [April 2, 2022, 7:52am UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/58 "2022-04-02T07:52:34Z")

</div>

I’m out. The lack of true accountability and ownership here is galling.

---

<div class="post-metadata">

**Author:** ![steenthsteenth](https://avatars.discourse-cdn.com/v4/letter/s/ac8455/32.png) [@steenthsteenth](https://forums.wyze.com/u/steenthsteenth)\
**Post date:** [April 2, 2022, 1:06pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/59 "2022-04-02T13:06:59Z")

</div>

From early on, there were questions about Wyze. I understand that they use Alibaba cloud service which would allow the Chinese government to access all recordings. Ignoring that (which is a big concession) this new disaster is incomprehensible. Wyze tiptoes and sneaks around plugging their leaky garbage products so that people keep buying. Clearly Wyze is not an internet hardware producer, you are a database manager, and we are your source of information. Who knows what or to whom you sell the data. So to quote [Gizmodo.com](http://Gizmodo.com): " \*\*If you have a Wyze [security camera](https://gizmodo.com/wyze-is-killing-support-for-its-original-security-camer-1848437045), **my suggestion would be to rip it out of the wall and throw it in the nearest trashcan"**

---

<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, 2:54pm UTC](https://forums.wyze.com/t/response-to-the-3-29-22-security-report/223865/60 "2022-04-02T14:54:46Z")

</div>

> [@steenthsteenth](#):
>
> From early on, there were questions about Wyze. I understand that they use Alibaba cloud service which would allow the Chinese government to access all recordings.

Nope. Just concerns over where the P2P director servers - that carry zero video traffic - were located. Nothing to do with Alibaba either.

> [@steenthsteenth](#):
>
> Who knows what or to whom you sell the data. So to quote [Gizmodo.com](http://Gizmodo.com): " \*\*If you have a Wyze [security camera](https://gizmodo.com/wyze-is-killing-support-for-its-original-security-camer-1848437045), **my suggestion would be to rip it out of the wall and throw it in the nearest trashcan"**

Moronic scaremongering writer Lucas Ropek has already backtracked after someone finally explained to him what a router is.

---

<div class="post-metadata">

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

</div>

You don’t need to be at all security savvy to have a router with NAT (all home routers have it) and thus be protected from this exploit. In fact, you’d need to be somewhat security savvy to have a camera that was actually vulnerable to this exploit from the internet, as you would have had to intentionally put the camera into a DMZ or forwarded port 80 to the camera in question. Now, if they are on your LAN, it’s a completely different story, but generally you have to assume that most devices on your LAN have at least a couple vulnerable ports open, with known default passwords or the like.  
It is notable that this vulnerability wasn’t protected by any authentication mechanism, but when hardcoded support admin usernames and passwords for most devices are leaked within weeks of their release to the security community, it’s not really any less secure than any other device on your network.

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

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