Multi-threaded javascript security implications

Question

Reading through this question on multi-threaded javascript, I was wondering if there would be any security implications allowing javascript to run mutliple threads. For example, is there a risk that a malicious script repeatedly generates a thread after a thread, trying to overload the operating system or interpreter and start entering the “w90> behavior area”, or is this not a problem to a large extent? Any other ways in which an attack could use a hypothetical javascript implementation that supports threads that a non-stream implementation will not be protected?

Update: Please note that blocking the browser does not match the creation of an undefined behavior exploit.

Answer 1

No, multiple threads will not add additional security issues to the ideal implementation. Threaded javascript will add complexity to the javascript interpreter, making it more likely to be used with an error. But not one of them is going to add any security concerns.

There are no topics in javascript because "Threads Suck" - read more from the language developer ( http://weblogs.mozillazine.org/roadmap/archives/2007/02/threads_suck.html )

Answer 2

, JS. , - .

, .

---

, , "undefined behavior"? , script , - , Gears, API Worker WorkerPool s, , .

Answer 3

, , javascript Google chrome ( JEEZ), , , javascript , , ( ) , , , Google , , javascript .

Answer 4

, 1) (, , -, ) 2) / JavaScript .

For # 2, I don’t see how this can really add any possible security problems for the engine / interpreter, unless there are flaws in the implementation.