News for hackers. Stuff that matters.
Re:If You Can’t Break Crypto, Break the Client: Recovery of ... by bengotow on Friday April 08, 2016 @01:31PM (#11456353)
Man, that's depressing. It's fairly easy to prevent this particular kind of injection—you just have to add a Content Security Policy to the HTML page. The appropriate value for web pages running from file://, with no expectation of downloading and executing remote JavaScript is: `script-src 'self';`

Really sad to see that Apple is using embedded web views without these sort of basic protections. I bet worse exploits than this are possible, given that they probably expose parts of the ObjectiveC layer through the JavaScriptCore bridge.

Re:If You Can’t Break Crypto, Break the Client: Recovery of ... by moloch on Friday April 08, 2016 @02:38PM (#11456848)
It gets even scarier with frameworks like nw.js where you can just execute native code directly from the DOM.