4 ms·
Exploitations like this are much more complicated than lacking bounds checking; after all most web exploits start by defeating the supposedly memory safe JS int
by astrange 6y ago
Exploitations like this are much more complicated than lacking bounds checking; after all most web exploits start by defeating the supposedly memory safe JS interpreter.
- pjmlp 6y agoBecause they trigger bugs in the underlying engine code written in C and C++.
- astrange 6y agoIf your JIT interpreter is written in a safe language it can still have memory bugs because it’s generating and executing assembly directly.
- wizzwizz4 6y agoThat sounds like a challenge.
- pjmlp 6y agoIt might, just like the microcode, firmware and hardware design can have such bugs. Safe languages don't magically make all code impossible to exploit, they just reduce the attack surface to logical errors, instead of having to deal with UB and memory corruption as well. The same way that helmets and belts don't save people from dying all in all kinds of accidents, yet they surely help reducing the mortality numbers. I enjoy languages with helmets and belts.