Now we have exploits for libraries and runtimes that often allow access to arbitrary application data. If this functionality is in a separate process without su

Now we have exploits for libraries and runtimes that often allow access to arbitrary application data. If this functionality is in a separate process without such privileges, application data will be safe. This will prevent the prior vulnerability. Will it prevent the next one? Do you know what it won't make the next vulnerability worse? A year or two ago I had to deal with a bunch of people complaining that the embedded device my team was selling was vulnerable to BEAST, because their scanning tool told them it was. I wrote a long essay for the support team about how BEAST is exploited and it's really hard to do it against a limited purpose control GUI with no publicly routeable address, and this worked for about half the people who complained. For the others we had to turn on RC4, which may have been even worse, but now their tool wasn't complaining at them so they were happy, even though they may have been worse off. Thankfully my old team didn't rush to the new OpenSSL version so they got to avoid the past 48 hours being complete shit for them. There aren't clean answers. Like with financial regulation, what you do to make sure the last thing never happens again may create the next thing.