- Related Stories
-
Microsoft patches may break Web sites
November 2, 2005 -
More trouble with Microsoft patches
October 20, 2005 -
Microsoft plugs Windows worm holes
October 11, 2005
The security bulletin is deemed "critical," Microsoft's highest risk rating, the company said in a notice posted on its Web site on Thursday. Last month's "Patch Tuesday" included nine bulletins covering 14 Windows flaws. Some of the patches have caused trouble for users since their Oct. 11 release.
Microsoft rates as critical any security threat that could allow a malicious Internet worm to spread without any action required on the part of the user.
Microsoft's notice did not specify which component of Windows is being repaired in Tuesday's bulletin or how many flaws the update will deal with. Security researchers have several unpatched flaws outstanding with Microsoft. For example, eEye Digital Security lists eight vulnerabilities on its Web site for which it considers fixes overdue.
In addition to the Windows security fixes, Microsoft also plans to issue at least two updates that it deems high priority, but that are not security-related, the company said.
Furthermore, as it does every month, a new version of the Windows Malicious Software Removal Tool will be released. The tool detects and removes malicious code placed on computers.
Microsoft gave no further information on Tuesday's bulletins, other than stating that the Windows update will require restarting the computer.
The Redmond, Wash., software giant provides information in advance of its monthly patch release day, which is every second Tuesday of the month, so people can prepare to install the patches.
Microsoft said it will host a Webcast about the new fixes on Wednesday at 11 a.m. PDT.
See more CNET content tagged:
bulletin, security, patch management, Microsoft Corp., Microsoft Windows




Someone decided a long time ago that software could never be 100% reliable (for a host of reasons, some of which still apply, many of which don't) so it should not be held accountable if it fails.
Therefore laws were passed that exempt software (and some other technologies, computers are probably included in the mix) from having to be 100% reliable.
The issue here is not whether software crashes, but whether someone can take advantage of the software crashing - i.e. buffer overflow.
Because the backbone of Windows is Explorer, if someone can cause it to crash with malicious code, they have direct access to your operating system and are able to run any piece of code they choose.
64-bit processors will mitigate this to some respect, as they are not supposed to allow any code to be executed when a buffer overflow occurs.
This doesn't mean all viruses will cease to be, just one (the most popular) avenue of attack could be shut down.
How well this is implemented remains to be seen, but a 64-bit OS is required to make use of the feature, and WinXP 64 is still only a beta.
Vista is supposed to be compliant, but we shall see.
Closed operating systems, such as the Mac OS, already operate in this way, which is why people say that it's impossible to create a Mac virus.
This isn't strictly true, but is close enough as almost all modern viruses use this avenue of attack (just as most viruses of the late eighties, early nineties were boot sector viruses).
So while the type of attack used today will probably be stopped cold with the next release of Windows, a new method of attack is only a few keystrokes away.
And that's basically it - 1/Software is protected by law to the extent that you can't sue if it proves to be faulty, and don't expect this to change and 2/For a short while things will get better when 64-bit processors and 64-bit operating systems are used by the majority of users, but 3/eventually these will be hacked too.
The truth is that more and more people are getting behind the idea of holding software companies and in some cases developers responsible for the stability and security of the software the produce. My only thought is for developers to become proactive and find ways to better secure their code either through specific supported platforms, better development tools and languages, or better system testing.
I know that at least two of them are unpopular with developers because of the inherent cost of doing them, but better to be proactive than sit around and complain about how nobody understand how hard it is to be a developer or how much it will cost and hinders software all together to be reliable, stable, and secure. I hate to say it, but those people that don't understand are lawmakers and everybody else. Those are the people that will push the lawmakers into making those laws. Be they right or wrong.
- Much appreciated!
- by Mister C November 8, 2005 10:22 AM PST
- I just wanted to say thanks. This is one of the few times where ideas we presented rationally and without name calling etc. (my OS is better, my browser is better yap, yap, yap). I only wish there were more talk-backs like this. Thanks!
- Like this Reply to this comment
-
(9 Comments)