|
|||||||||||
|
RE: forbidden functions on client-side scripts
From: Thor Larholm <Thor(at)jubii.dk>
Date: Fri Dec 13 2002 - 07:21:17 EST
Any practical reallife exploitation of these 'forbidden' functions would most surely involve anything from simple to advanced string obfuscation, such as generating the function call or object reference dynamically or producing the code to be executed from compressed strings that are recreated and evaluated at runtime. Since your content filter merely does simplistic string matching, not unlike most AV vendors when they filter 'nasty' POC code from Bugtraq, it will only detect the most crudest attempts from the most inexperienced script kiddie. Other than that, the only functions in your list that are actual VBScript and JScript functions are CreateObject and ActiveXObject, the rest are methods that exist on commonly used ActiveX object - after their successful instantiation.
Regards
-----Original Message-----
Some products that are used as content filters for the HTTP traffic used by internal users, have the ability to block certain "dangerous" functions used on client side scripts from getting to the internal client. Attached is the default function list used by such a product. Since I'm not a programmer, can someone tell me if this list is complete/overkill/lacking and what other functions that are dangerous/benign should I consider adding/dropping from the list. The list is given for VBscript and Javascript separately. [VB SCRIPT]
[JAVA SCRIPT]
TIA, Shimon Silberschlag
+972-3-9352785
This archive was generated by hypermail 2.1.8 : Wed Aug 23 2006 - 14:07:46 EDT |
||||||||||
|
|||||||||||