Ethical Hacking

Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package.
Computer Forensics Training at InfoSec Institute

Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors.




Network Security NTBugtraq
[Top] [All Lists]

Change to Object Caching in IE with XP SP2 applied

Subject: Change to Object Caching in IE with XP SP2 applied
Date: Fri, 25 Feb 2005 13:36:24 -0500
One item that Microsoft has changed in IE with XP SP2 is the disabling
of Object Caching. Very little information exists on the overall
security implications of Object Caching although Greymagic did release
an advisory on possible exploits using Object Caching:
http://www.greymagic.com/security/advisories/gm012-ie/

Disabling Object Caching seems like a no brainer but it looks like it
might cause subtle errors with JavaScript since scripts will return
different results depending if it's on or off. See KB below for details:
http://support.microsoft.com/Default.aspx?kbid=884697
http://support.microsoft.com/Default.aspx?kbid=884698

NOTE: The sample script in kb 884697 needs to be changed to work
correctly (ie show the differences). You need to change the frame
reference from 2 to 1.

My question to the NTBUGTRAQ readers is if anyone has seen issues with
their JavaScript after disabling Object Caching and if anyone can shed
some more light on the real security significance of leaving Object
Caching enabled.

Thanks in advance,

Don

--
NTBugtraq Editor's Note:

Most viruses these days use spoofed email addresses. As such, using an 
Anti-Virus product which automatically notifies the perceived sender of a 
message it believes is infected may well cause more harm than good. Someone who 
did not actually send you a virus may receive the notification and scramble 
their support staff to find an infection which never existed in the first 
place. Suggest such notifications be disabled by whomever is responsible for 
your AV, or at least that the idea is considered.
--

<Prev in Thread] Current Thread [Next in Thread>