News for hackers. Stuff that matters.
Re: by bluesign on Tuesday June 25, 2024 @02:56PM (#40792156)
To be fair to telegram; similar things happened to many big names: facebook, google, apple etc
Re: by lxgr on Tuesday June 25, 2024 @03:21PM (#40792477)
Delivering messages to the wrong recipient!? Examples, please!
Re: by wiseowise on Tuesday June 25, 2024 @04:00PM (#40792926)
How could client deliver messages to the wrong recipient? Why would client have messages for user outside of the one logged in anyway?
Re: by ascar on Tuesday June 25, 2024 @04:32PM (#40793256)
Seems like a rather easy thing to go wrong in the client, no?

User sends message via client. Client fumbles the recipient id. Message ends up at the wrong recipient.

Examples: incorrect recipient ID attached to contact in list where users selects recipient. Buggy selection of multiple targets in the selection UI due to incorrect touch event handling. Incorrect deletion of previously selected and then deselected recipient from recipient array of multitarget message. Or if working low level even a good old off by one error and reading out of bounds data for the recipient list (though that one hopefully should trigger a faulty send request due to other stuff no longer matching). There is endless examples.

The server can't really safeguard against the client providing a legitimate send request even though the user intended to send it to another recipient.

Re: by webappguy on Tuesday June 25, 2024 @03:49PM (#40792780)
Curious to know more. Will search but if anyone finds anything
Re: by bluesign on Wednesday June 26, 2024 @05:52PM (#40805023)
There are many examples, I posted one to parent. Usually it effects some small percentage of users. But size of the team or company not directly solving the problem.
Re: by ChrisClark on Tuesday June 25, 2024 @04:02PM (#40792951)
https://news.ycombinator.com/item?id=27950763

Yeah, I don't know how they manage to get bugs like that, but it's happened