[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ntbugtraq
Subject:    Change to Object Caching in IE with XP SP2 applied
From:       Don Tuer <don.tuer () CGI ! COM>
Date:       2005-02-25 18:36:24
Message-ID: 02fd01c51b68$e8ca06b0$5140350a () csb ! cginet
[Download RAW message or body]

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 list] [next in list] [prev in thread] [next in thread]