I was told that if you use global objects in a Javascript that it possible that a malicouse user could exploit the web page. Would this be true even with static web pages?

Hi dman777,
The problem using global variables is the NameSpace cluttering (efficiency loose) ans libraries conflicts, no necessarily exploits. But if there is any exploitable bug, it will be easier to exploit if you use global variables. See http://www.javascripttoolbox.com/bes...ces/#namespace for more details and good JS practices (or use Google for it).

There is no difference between static or dynamic pages (browsers don't really know where pages come from). But, of course, if it's a static page there is no DB and, therefore, there are no users, passwords, etc. Might still be other bugs or sensible data, or other apps in the same server that could still be exploitable by JS bugs in the static page.

Hope it helps.

Did whoever told you this give you an example of such an exploit?

no, it was on freenode so you know...your lucky to get an answer and what answers you get you don't want to make anyone made and get flamed.

I've never heard of a Javascript global object exploit, and my nose tells me that this exploit does not exist. I mean, is the ubiquitous jQuery global variable an attack vector?

No, absolutely. The exploitable bugs are in the server side, when some controls are left to javascript instead of doing it in server side, too. Whenever I load a page on my browser (Firefox, Chromium), I always can tell the browser to execute customized JS code (with Firebug on FF or Developer tools on Chromium). So JS is not where exploitable bugs live, it's always on server side. JS is there just to help the user, so you cannot delegate security matters only to JS.