Last Friday, Wyze experienced service outages that reportedly gave about 13,000 users the ability to view event thumbnails and, in some cases, videos from other users' cameras.
On Monday morning, Wyze sent an email claiming that 99.75% of accounts were unaffected.
** ****** *******, ** *** * service ****** **** *** ** * security ********. **** ******* *** **** 99.75% ** *** **** ******** **** not ******** ** *** ******** *****, but ** ****** ** **** *** aware ** *** ******** *** *** you **** **** ** *** ***** to **** **** ** *****'* ****** again.
*** ****** ********** **** *** ******* AWS *** **** **** **** ******* for ******* ***** ***** ****** *******. If *** ***** ** **** **** cameras ** ****** ****** **** ****, you ****** *****’* **** **. **’** very ***** *** *** *********** *** confusion **** ******.
** ** ****** ** ***** ******* back ******, ** *********** * ******** issue. **** ***** ******** ****** *** wrong ********** *** ***** ****** ** their ****** ***. ** *********** ******* access ** *** ****** *** *** started ** *************.
** *** *** ******* **** ** cameras **** ****** **** ******, ***** 13,000 **** ***** ******** ********** **** cameras **** **** *** ***** *** and *,*** ***** ****** ** ****. Most **** ******** *** *********, *** in **** ***** ** ***** ***** was **** ** ** ******.
**** ** *** ****** **** ** ~5 ****** ******** ***** **** ************** ********** ***, ** **** *****, video **** ******* ********* ** ***** users.
**** ****** **** **** *** *** device *** **** ***** ** ** unprecedented **** ********** ** * *****-***** library.
*** ******** *** ****** ** * third-party ******* ****** ******* **** *** recently ********** **** *** ******. **** client ******* ******** ************* **** ********** caused ** ******* ****** **** ****** all ** ****. ** * ****** of ********* ******, ** ***** ** device ** *** **** ** ******* and ********* **** **** ** ********* accounts.
*******, ** *********** ** ********* ***** which *****-***** ******* *** *** *** device ** *** **** ** ***** be ***** **.
** ********** **** ******, ***** ** **** ********** ***** what ******** ****** *** ******** *****.
**** *** ****** ** *** **** ID *** ** ***** **, ***** should ** ********** ******, * ***** a ***** ***** ********* ***** ** likely, ********** ******** ****** ** ***** ********* **** ***** ****** ** ******* users ** *** ***.
** **** ** ** *** ***** reports ** **** **** *** ****** tab. ** **** ***** ** ** extra ***** ** ************ *** **** user ****** **** ***** *** **********. To ** ***** ****, ** *** now ***** ******* *** *** ***** who **** **** *** **** *** today ** ***** ******.