> Wyze blamed "a third-party caching client library that was recently integrated into our system" for the trouble. Yes, of course. Blame a third party library which was probably created by an open source maintainer instead of testing your own systems.
Wyze security incident update
91–100 of 161 posts
Re: Wyze security incident update
#92Re: Wyze security incident update
#93> Wyze blamed "a third-party caching client library that was recently integrated into our system" for the trouble. Yes, of course. Blame a third party library which was probably created by an open source maintainer instead of testing your own systems.
Re: Wyze security incident update
#94> Wyze blamed "a third-party caching client library that was recently integrated into our system" for the trouble. Yes, of course. Blame a third party library which was probably created by an open source maintainer instead of testing your own systems.
Re: Wyze security incident update
#95I have my cameras blocked from the internet and doing backups in the attic.
Re: Wyze security incident update
#96Why do people have cameras inside their house anyway?
Re: Wyze security incident update
#97Why do people have cameras inside their house anyway?
Re: Wyze security incident update
#98Re: Wyze security incident update
#99This actually looks like a concurrency bug in their request handling code that may have stored the user id and camera id in shared variables, under load the wrong camera id is seen by a user. At least based on the description of what they say happened.
Re: Wyze security incident update
#100I have my cameras blocked from the internet and doing backups in the attic.