3 ms·
Hmm, If one wishes a broad formulation for computer Hijacking, I would say that it's a mismatch between input-scanning and interpreter behavior. This view woul
by joe_the_user 12y ago
Hmm,
If one wishes a broad formulation for computer Hijacking, I would say that it's a mismatch between input-scanning and interpreter behavior. This view would include both SQL-injection and buffer-overruns (while the interpreter is the chip itself).
Of course something like Heartbleed is a bit different because it's around extract data that shouldn't have been there in the first place.
But still, some kind of "interpreter" is needed for any language and challenge is to make sure that user-input remains "data" as the interpreter understands it. This "sanitizing" is an ultimately hard problem even as each version of the problem (preventing buffer overruns, prevent sql-injection, etc) seems easy.
Security similarly is hard in that finding all weak points and strengthening them is hard even as strength weak-point-X may seem easy.