0

I just read about Caja, which is a "sanitized" version of JavaScript. But I'm wondering - what is the big problem with JavaScript(it seems so widely used )? Just how dangerous is it?

closed as too broad by gnat, user40980, user53019, user22815, Wayne Molina Sep 1 '14 at 0:52

Please edit the question to limit it to a specific problem with enough detail to identify an adequate answer. Avoid asking multiple distinct questions at once. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.

  • 2
    It appears to me the main difference here (security wise) is it does not give direct exposure to the DOM. Which will (in theory I suppose) negate silly errors introduced by some developers. – rlemon Mar 29 '12 at 23:17
3

The changes it makes vs. regular javascript are pretty well described here.

From that reference:

Caja takes JavaScript (technically, ECMAScript 5 strict mode code), HTML, and CSS input and rewrites it into a safe subset of HTML and CSS, plus a single JavaScript function with no free variables. That means the only way such a function can modify an object is if it is given a reference to the object by the host page. Instead of giving direct references to DOM objects, the host page typically gives references to wrappers that sanitize HTML, proxy URLs, and prevent redirecting the page; this allows Caja to prevent certain phishing attacks, prevent cross-site scripting attacks, and prevent downloading malware. Also, since all rewritten programs run in the same frame, the host page can allow one program to export an object reference to another program; then inter-frame communication is simply method invocation.

And, Google's site on Caja.

Not the answer you're looking for? Browse other questions tagged or ask your own question.