Comment by DANmode
2 days ago
The user opens a WhatsApp link (or executes a file sent to them), Chrome WebRTC is exploited, shellcode invokes a Windows Kernel race condition, process escalates to Kernel/System privileges, Windows sandbox is bypassed, allowing the malware to drop the IME DLL and initialize the COM hijacking loop.
Memory safety, and a number of other glaring holes in common stacks, are ignored by the general public for the same psychological and effort-related reasons that people secure their whole lives with easily-picked Schlage locks, or windows/doors that can be defeated in under 5 seconds, often silently.
Most genuinely do not or can not believe tragedy can find them - until it has.
> Most genuinely do not or can not believe tragedy can find them - until it has.
I'm not exactly surprised that vulnerabilities like this are possible. I just wanted the details. Thank you. "WebRTC was vulnerable and allowed access to a longer exploit chain" is the important part in my view.
> Memory safety, and a number of other glaring holes in common stacks, are ignored by the general public
I would venture that "the general public" has no concept of "memory safety" in the first place.
Safe computing in general.
All a game, with liabilities abstracted away to customer service and two factor texts.