> 34 security vulnerabilities in WebAudio due to use-after-free and out-of-bounds errors
This is what happens to any language that builds on C's compatibility.
This is what happens to any language that builds on C's compatibility.
In sane languages an out-of-bounds error causes program termination, unless it was disabled on purpose (assuming it can be disabled). In C anything goes.
An out of bounds can cause the program to be injured, but not die, and eventually have some kind of inconsistent state.
> use-after-free happens in almost every language that is not gc'ed.
Yes, true if we are speaking about Modula-2 or Extended Pascal dialects. The most notable alternatives to C with manual memory management.
Everything else has at very least reference counting support.
object = create_object() // RC 1
object.release() // RC 0 => will be released
// ...
object.doSomething() // Used after object was released
?