6 ms·
> Need to keep old insecure code around That's what process boundaries are for. (As a bonus, you get protection from any Spectre-like issues arising in the old
by zozbot234 7y ago
> Need to keep old insecure code around
That's what process boundaries are for. (As a bonus, you get protection from any Spectre-like issues arising in the old code.)
- saagarjha 7y agoNot everything can be neatly refactored out of a process.
- pjmlp 7y agoProcess boundaries don't protect against internal exploits, which is what most of the C and C++ exploits are all about. If you are able to force a process to change its behaviour, the process boundaries become useless.
- saagarjha 7y agoProcess boundaries specifically protect against these exploits.
- pjmlp 7y agoSo how does a process boundary protect against Heartbleed?
- saagarjha 7y agoProcess boundaries help you when you start jumping through a ROP chain that spawns a shell because your process doesn't have access to things that it shouldn't, even when compromised. Calling Heartbleed an example of a process "changing its behavior" doesn't really make sense in the context of exploits that can cause arbitrary code execution.
- pjmlp 7y agoSo each one gives an example that suits their own sales pitch.
- dx87 7y agoYou don't have to spawn a shell as a seperate process. Injecting and executing code inside a vulnerable process has been done for a long time.
- saagarjha 7y agoA shell spawned in an unprivileged process is not very useful.
- pjmlp 7y agoOne doesn't need to spawn a shell.
- iCodeSometime 7y agoInjecting and executing code inside an unprivileged process is not very useful.
- pjmlp 7y agoSome black hats would consider stealing data, data corruption or triggering DOS already very useful for ransonware.