quietman7
Jul 29 2009, 07:10 AM
QUOTE
Microsoft issued two emergency updates on Tuesday to fix critical security bugs that leave users of Internet Explorer and an untold number of third-party applications vulnerable to remote attacks that completely commandeer their computers...
http://www.theregister.co.uk/2009/07/28/mi...tches_released/Microsoft Security Bulletin MS09-034 - Critical
Cumulative Security Update for Internet Explorer (972260)
http://www.microsoft.com/technet/security/...n/MS09-034.mspx
Andrew
Jul 29 2009, 04:49 PM
Bugger, that's nasty looking. You know it's bad when MS releases a patch outside their regular cycle.
scff249
Jul 29 2009, 05:49 PM
So that's what that update was for that I got last night.....
Also....what is their regular cycle again? The first Tuesday of the month or something? I can't quite remember.
jchedot
Jul 29 2009, 07:00 PM
Second Tuesday of the month.
samuel3
Jul 29 2009, 08:52 PM
I got the update today? Why a day late? Or whenever it was out? (Witch is longer)
Romeo29
Jul 30 2009, 12:35 AM
The bug was caused by a typo by Microsoft programmers. They typed an extra ampersand (&).
QUOTE
"The bug is simply a typo," Michael Howard, a principal security program manager in Microsoft's security engineering and communications group, said in a post Tuesday to the Security Development Lifecycle (SDL) blog. Howard, who is probably best known for co-authoring Writing Secure Code, went on to say that the typo -- an errant "&" character -- is the "core issue" in the MSVidCtl ActiveX control.
http://www.computerworld.com/s/article/913...t?taxonomyId=85
QQQQ
Aug 11 2009, 08:57 AM
I have had that patch cause an issue on Windows 2000 PC's, 4 that I know of so far. Users called me with trouble connecting to the internet with Internet Explorer. Upon launching IE it would open, then close immediately. Then a download file prompt popped up like it wanted to download something, I thought it was malware related at first. The internet properties (options)were missing 3 tabs, security , privacy and content. Rebooting resolved the issue on all 4 computers.