Virus Alert: Internet Explorer 7 vulnerable to drive-by downloads
Security researchers are warning that serveral thousand websites are taking advantage of a "zero-day" vulnerability spotted in Internet Explorer. John Stokdyk reports.
According to IDG's Robert McMillan, the flaw in how Internet Explorer handles XML (Extensible Markup Language) was initially discussed on a Chinese language website more than a week ago.
Continued...
The full article is available to registered AccountingWEB members only. To read the rest of this article you’ll need to login or register.
Registration is FREE and allows you to view all content, ask questions, comment and much more.
Or if you are already registered, login here
Better still, don't patch it, ditch it
Better still, don't patch it, ditch it and use Mozilla Firefox 3. It's FREE and better still NOT Microsoft and that says a lot!
Explorer patch - BEWARE
Yesterday afternoon (18.12.08) we found that our networked Sage personal tax suite wouldn't work. The workstations timed out when trying to access the SQL Sage database. After more than 4 hours on the Sage help line and 2 hours of a Sage expert's time, we were told this morning that the registry settings on each workstation had to be changed. It seems that the IE patch is so secure, it won't let you access parts of your own server.
No need to panic
.
A security patch will become available tomorrow, (17/12/08) at 1 p.m. EST at the Microsoft Update site and at the Microsoft Download Center.
Trust me!

Undetected for 9 years ....
So realistically rushing to patch at this stage is rather late in the day ...
http://www.computerworld.com/action/article.do?command=printArticleBasic&taxonomyName=Security&articleId=9124174&taxonomyId=17
and the issue is 'training' - despite M$ having set itself up as the arbiter of standards !
What's more M$ have just found a problem with SQL Server going back to 2000
http://news.cnet.com/8301-1009_3-10128475-83.html
We really should have a system of liability with software - the potential risks & resulting damage or time spent patching should be attributable to M$ and not down to the end user to underwrite their mistakes