News for hackers. Stuff that matters.
Re:Wyze security incident update by gerwim on Monday February 19, 2024 @05:05PM (#39435394)
> 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 by _obviously on Monday February 19, 2024 @05:17PM (#39435499)
Of course, the reason this keeps happening is the infrastructure is designed to let it happen in certain cases. Notice how they explicitly say, they need to fix it in the front end. They can't fix it in the backend because that would break eavesdropping.
Re:Wyze security incident update by cromka on Monday February 19, 2024 @07:34PM (#39436617)
That’s a bit tinfoily take
Re:Wyze security incident update by summarity on Monday February 19, 2024 @05:12PM (#39435453)
Also "was recently integrated" - by ... magic?