News for hackers. Stuff that matters.

A comment on Wyze security incident update. Parent comment

Re:Wyze security incident update by quatrefoil on Monday February 19, 2024 @12:24PM (#39432280)
It's not even that: the quoted language doesn't even blame the library - it appears to blame increased load.

"As a result of increased demand, it mixed up device ID" - no, it mixed up IDs as a result of some sort of a concurrency bug. I don't understand the point of deflecting this far.

[ Parent | on HN ]
Re:Wyze security incident update by matthewcford on Monday February 19, 2024 @12:48PM (#39432553)
Likely to be a multi-threading issue; my bet is the cache client wasn't thread-safe. I've seen this in some apps before and the solution was to turn off multi-threading while we debug the library that was causing the issue.
[ Parent | on HN ]
Re:Wyze security incident update by sabujp on Monday February 19, 2024 @03:46PM (#39434607)
This is the answer!
[ Parent | on HN ]