Stop Microsoft
All Things Microsoft => Microsoft as a Company => Topic started by: voidmain on 13 December 2002, 03:36
-
http://www.theregister.co.uk/content/55/28546.html (http://www.theregister.co.uk/content/55/28546.html)
quote:
Your Microsoft critical security patches tonight
By John Leyden
Posted: 12/12/2002 at 17:15 GMT
Microsoft last night released three sets of security patches, the most important of which aims to address flaws in Microsoft Virtual Machine (VM) which it admits could enable system compromise.
The VM patch is designed to address eight vulnerabilities, the most serious of which would enable an attacker to gain control over a user's system. That's possible because of a vulnerability that means an untrusted Java applet could access COM objects.
Microsoft VM is a virtual machine for the Win32 operating environment and ships with most versions of Windows as well as in most versions of Internet Explorer, so many millions of users are potentially affected by the problem. Attack scenarios are all too familiar. To exploit the flaws an attacker would create a Web page that, when opened, exploits the desired vulnerability, and either host it or send it to a victim as an HTML mail.
No surprise then that Microsoft describes the patch (which can be found by following the link here) as critical.
Next up there's a patch for a privilege elevation flaw - a particular Windows message, called WM_TIMER. Because of this problem an attacker able to log onto a target machine could gain administrator privileges.
The issue affects Windows NT 4.0, NT 4.0 Terminal Server, Win 2K and Win XP. The big mitigating factor here is that the flaw looks far from easy to exploit, particularly because it doesn't lend itself to remote exploitation. For these reasons, Microsoft rates the flaw as important but not critical. There's more info on this problem here.
Lastly, while we're doing a bug roundup, we should mention a
"moderately severe" vulnerabilitywithin Windows Server Message Block (SMB) protocol which could enable group policy on domain controllers to be modified. Flaws in cryptographic signing implementation used by MS in SMB are the root cause of the problem. These flaws are fixed in Win XP SP1 or through a separate patch, released yesterday, which is designed to address the problem on Windows 2000 boxes.
That's all for now.
Have a nice day.
-
I was reading this story at another site. The headline was critical flaw something or other. I was reading through and I realised they were trying to put a nice face on numerous bugs, most of which were serious in nature. By the time I hit the bottom I was laughing myself silly. Integrate IE what a fantastic idea. ha ha ha ha.
I am thinking SP2 will soon come out (or is it 4 now - I forget now that my home computer doesn't use Windows anymore).
-
So, what do you guys think is larger: the combined Windows code since the start of MS, or the entire list of all bugs in all those versions?