3 ms·
The difference is that Javascript generally has no API for accessing file system and OS resources, but Java applets by default give full access to the entire Ja
by meowface 13y ago
The difference is that Javascript generally has no API for accessing file system and OS resources, but Java applets by default give full access to the entire Java standard library; it simply restricts certain parts of it with the sandbox. If a Java applet can find a way to access things on the blacklist, then it can download and run any file with your OS user privileges.
With Javascript there isn't actually a sandbox to break out of.
- kleiba 13y agoIs there an implementation of the JVM in Javascript? That should address some of the issues outlined.
- pjmlp 13y ago> API for accessing file system and OS resources You mean like FileReader and WebGL/CL?
- free652 13y agoAnd so it can be exploited: http://www.scip.ch/en/?vuldb.10561 http://www.scip.ch/en/?vuldb.10561
- meowface 13y agoThis is a buffer overflow exploit in the browser, not an exploit of the API mechanics. On the other hand, most critical Java vulnerabilities are simple sandbox bypasses, not memory corruption ones.
- pjmlp 13y ago> Java vulnerabilities are simple sandbox On Oracle's implementation. There are other JVMs to choose from. Plus, can you guarantee that the JavaScript sandbox from all VMs are safe if hackers turn their attention to them?
- meowface 13y agoIBM's JVM and OpenJDK's IcedTea have fallen victim to most (possibly all, not sure) of the exact same sandbox bypass flaws as the ones in Oracle's HotSpot, mostly because the codebase of all the other alternatives still contains a huge portion of Oracle's original code.