4 ms·
There's a risk that someone had been sitting on a sandbox escape that assumed having RCE inside the sandbox first, and so they'd been waiting for an RCE exactly
by pizlonator 29d ago
There's a risk that someone had been sitting on a sandbox escape that assumed having RCE inside the sandbox first, and so they'd been waiting for an RCE exactly like this one.
Those folks would not be disclosing their sandbox escape unless they were good guys.
(Posted with a memory safe WebKit, Fil-C FTW)
- pizdocalmin 29d ago[flagged]
- oynqr 29d agoYou should add a disclaimer that you are the CEO of Fil-C. /s In the context of this vulnerability, I doubt memory safety would have made much of a difference. This is a great reminder though, currently doing a full userspace replacement on my 3D printer and Fil-C might be just what I need for the irreplaceable C parts.
- pizlonator 28d agoHow would memory safety have not made a difference?
- iTokio 27d agoType confusion, leads to using an object in memory with the wrong type, that means accessing memory with a different layout, like an out of bounds buffer. So I think memory safety does matter in that case.