Microsoft Patches 19 Flaws, 6 in Vista

Cheesy Balogna writes "Microsoft has just released seven advisories — all rated critical — with patches for at least 19 vulnerabilities affecting the Windows operating system, the widely deployed Office productivity suite and the dominant Internet Explorer browser. Six of the 19 vulnerabilities affect Windows Vista. 'There are patches for 7 different vulnerabilities that could lead to code execution attacks against Word, Excel and Office. Users of Microsoft Exchange are also urged to pay attention to one of the critical bulletins, which cover 4 different flaws. A cumulative IE update addresses six potentially dangerous bugs. There are the six that apply to IE 7 on Windows Vista. The last bulletin in this month's batch apples to CAPICOM (Cryptographic API Component Object Model) and could also put users at risk of complete system hijack attacks.'"

Comments

Most secure windows ever!

[A beautiful mind]

Hm...I guess they leveraged the active synergies to stop the probes but the active hardening failed on the SuperHyperVista3000 edition.

Oh wait, you did expect real security instead of buzzwords?

Re:Most secure windows ever!

[BrewedInTexas]

Actually I expect a bunch of monday morning quarterbacking from a horde of slashdot users who should be working. Ah, the day after patch tuesday.

You've got some serious issues with the days of the week.

Linux patches?

[stevenbdjr]

When are we going to start seeing regular Slashdot postings outlining Linux or other free software security patch releases in the same accusatory tone that the monthly Microsoft security bulletin releases bring? No, I'm not trolling, but I'm getting sick of the clear bias Slashdot editors (and most readers) have when it comes to matters of Microsoft.

(I can feel my karma slipping away, but I couldn't take it anymore).

Re:Linux patches?

[varmittang]

We do, its usually for Firefox bugs, because that is Linux to the rest of the world. But then comes the trolls that point out that it was fixed in a matter of hours and not weeks or months.

Re:Linux patches?

[A beautiful mind]

If the linux kernel people would ignore vulnerabilities, downplay them, take months for them to produce a fix, merge distinct vulnerabilities into single advisories and finally try to claim improved security, then I'd guess I would want to see stories about it on slashdot. So what bias?

Re:Linux patches?

[*weasel]

Probably when they gain a practical monopoly on desktop computing, begin heavily abusing their users and illegally wielding their market control against the rest of the industry.

Re:Linux patches?

[snoyberg]

You're right, Slashdot is biased against Microsoft. If you're looking for unbiased news stories, you've come to the wrong place.

Re:Linux patches?

[Reivec]

How is this an "accusatory tone"? Looks to me to just be stating the fact that there are some major security patches released that windows users should know about. Microsoft would WANT this information to be spread around so that people patch up and have fewer problems thus relating fewer poor experiences to a Windows problem.

Perhaps you are showing your own bias?

Re:Linux patches?

[QuickFox]

But then comes the trolls that point out that it was fixed in a matter of hours and not weeks or months. Don't blame it on the trolls, they only report it here. It's the open-source developers' fault. Why can't they wait for some time and give Microsoft a chance?

Re:Linux patches?

[Lord_Slepnir]

You have listed my fondest dream: To be part of an abusive monopoly that replaced the abusive monopoly that I hated when I was a young college student....*sigh*

Re:Linux patches?

[EvilRyry]

It's not really trolling if its true (which it often is). Then there's also the differences in how each group determines whats a vunerability. Fedora Core for example patches many security issues (and they get counted as such) even when they don't really effect the distro due to things like ExecShield.

Re:Linux patches?

[SnowZero]

It's a myth that Slashdot has almost all Linux users. It used to be that way, but it has long since been overrun with a more "general computing" crowd. I would bet that if you add up the regular Windows and Mac users, it would outnumber regular Linux users. For UIDs below 100k however, you would probably see a quite different statistic. People only notice Linux users here because we're not at 1-2%, like on almost any other discussion site.

Frankly, I'm now getting tired of the number of posts with the same tone as yours. You lament losing Karma in a sea of angry "Linux-zealot" mods, but I would guess you will be modded up, not down. Enjoy the karma...

Re:Linux patches?

[just_another_sean]

I see the recent batch of articles about MS patches as a response to the release of Vista. MS decided that the heavily enhanced security in Vista was worthy of a ton of press so I think it's fair that /. or any other tech site keep track of the validity of these claims, especially in the begining while MS's statements concerning Vista security are still fresh.

Although I do believe that MS made some good improvements to security in Vista it would seem that it's actual performance falls short of their claims. My bias comes from a real desire for security. As an IT guy who administers Windows and Linux boxes I'm interested in stories concerning both. But I think it's fair to state that MS's track record on security warrants a lot more security then Linux.

Re:Linux patches?

[suv4x4]

If the linux kernel people would ignore vulnerabilities, downplay them, take months for them to produce a fix, merge distinct vulnerabilities into single advisories and finally try to claim improved security, then I'd guess I would want to see stories about it on slashdot. So what bias?

Right there in the first sentences of that quote, that bias. Those are released patches, not "downplayed patches" or "ignored vulnerabilities". Those are actual fixes, released on a monthly basis.

If Microsoft would ignore it, we get "microsoft ignores it!" article on Slashdot. If they release a patch, we get "omg critical patch for Windows" article on Slashdot.

It's ridiculous.

Also how about claims of security and bending truth, just like you prove it yourself, Linux fanboys twist the truth about Linux far more often than Microsoft does with Windows. Anything goes.

Re:Linux patches?

[drinkypoo]

Right there in the first sentences of that quote, that bias. Those are released patches, not "downplayed patches" or "ignored vulnerabilities". Those are actual fixes, released on a monthly basis.

Microsoft has frequently been caught knowing about a bug for months before a patch is released.

When they get caught they claim they're doing QA, but past experience with Microsoft patches suggests that they are doing no valuable testing anyway.

If they had ever demonstrated trustworthiness, they might be trusted a bit. As it is, they have demonstrated time and again that they will fuck you over and lie about it.

If you appreciate the way Microsoft treats you, then you are free to sing their praises. But it doesn't make you right.

Re:Linux patches?

[Magneon]

The problem with this is that Linux patches generally happen individually as soon as the problem is discovered. This way your favorite distro can check on the individual components and alert you to the fact that there are updates. Microsoft on the other hand likes to release a bunch of patches at once, leaving the user vulnerable for a period of hours, days and sometimes weeks.

So no, we don't see 100 preemptive individual patch stories for various linux builds on here every day.

Re:Linux patches?

[TommydCat]

I didn't read anything accusatory or noted a demeaning tone in the summary. I think many here bring their own bias ready to start an argument (either for or against). To me, the summary is just stating that patches are now available, they are labelled "critical", and the users of this site may be interested as many of them own, use or deal with Microsoft operating systems on a daily basis.

What conclusion is the summary supposedly spoon-feeding me?

Re:Linux patches?

[abigor]

Slashdot is CmdrTaco's blog site. It is biased by its very nature. It makes no claims to objectivity or to be a "true" news site. To put it another way, it's an opinion site by design.

Re:Linux patches?

[suv4x4]

Microsoft has frequently been caught knowing about a bug for months before a patch is released.

When they get caught they claim they're doing QA, but past experience with Microsoft patches suggests that they are doing no valuable testing anyway.

If they had ever demonstrated trustworthiness, they might be trusted a bit. As it is, they have demonstrated time and again that they will fuck you over and lie about it.

If you appreciate the way Microsoft treats you, then you are free to sing their praises. But it doesn't make you right.

That's what pisses me off with fanboys: they don't get context at all. For them any article with "Microsoft" in it, is a reason enough to recycle the entire 30 years of Microsoft faults in a single post. Over and over.

Let's see what's the event at case: regular monthly patches for Windows. That's it.

I, and some other people just asked for objective opinions: there's no "ignored vulnerability" or "delayed responce" in THIS ONE CASE. There is NO reason to regurgitate past faults of Microsoft every single month, when completely predictably, the patches are released.

But all of those are treated as an excuse for doing just that.

So you response is that "I'm singing praises for Microsoft". There's basically no way to argue with you guys. Keep living in your imaginary world, I hope you're happy there.

Re:Linux patches?

[QuickFox]

While it's not exactly a security problem What makes you think it's not about security? If the ethernet driver locks up nobody can hack you.

Re:Linux patches?

[PixieDust]

I invite you to investigate this site which holds no immediate bias in it's reporting of security advisories, patches, problems and exploits. Look at the average turnaround time for patches, fixes, and responses to security problems. You will find out that Microsoft isn't as bad as everyone likes to pretend it is, nor is it's flagship Windows OS. Also to, I find it ironic that whenever someone points out a problem that affects Linux, people are like "But that's not the OS, it's (insert kernel module, driver, app, whatever) that is (insert special circumstance here).", but when it's Microsoft, they're all lumped together as "OMGz! Windoze h4x!". This includes vulnerabilities in Word, and Excel (and something else from the Office Suite, can't remember though atm), and additionally mentions Exchange. Exchange runs on a server platform, but ok, I'm not going to get into semantics on that (I assume they meant Outlook, though even if it was Exchange, it's still a fix, or at least an attempt at one).

I am the first to admit that Microsoft has problems with security, but it's a problem that plagues the entire industry. Linux, Unix, Windows, Mac, websites, forms, applications, EVERYTHING. It's a problem in how the industry approaches security. It goes far beyond Microsoft. The entire industry has this "Get it working now, patch it later" mentality. It's the "Default Allow" instead of "Default Deny" approach. There is NO reason Buffer Overflow attacks should work... EVER. Period. How hard is it to check your buffers, and make sure you're handling them properly? Very sloppy. Microsoft certainly isn't the best, but they're far from the worst. Don't believe me? Check that website, and all the security advisories for the past few years, and you will notice and interesting trend.

Re:Linux patches?

[tknd]

Frankly, I'm now getting tired of the number of posts with the same tone as yours. You lament losing Karma in a sea of angry "Linux-zealot" mods, but I would guess you will be modded up, not down.

But that's the problem. Had he not posted in that type of tone, he might not have gotten modded up. I've seen many good posts defending Microsoft products without flaming the opposition yet when they hit the 4 or 5 moderation marks, people keep trying to mod them down.

I'm sure even if you removed all of the modded up Funny posts (which often are stabs at MS but cloaked with humor) I'm sure you'd see a clear anti-MS bias in moderation. That is, you're more likely to get modded up if you choose to post anti-MS comments.

People here are also quick to mod up any frustration with MS products even when they're just flames, yet when you see the comments about frustrations for Apple or Linux, you often get responses to the person having frustrations showing good light for Apple/Linux/etc modded up, not the parent frustration.

Re:Linux patches?

[Richard_at_work]

Yes, they are regular monthly patches. That means that they are withholding completed patches until the chosen day comes.

Microsoft used to release as and when. They got slated on Slashdot for it.

Microsoft then rolled patches into a monthly patch. They got slated on Slashdot for it.

Microsoft released some important patches outside of the monthly cycle since they switched to it. They got slated on Slashdot for it.

Yeah, theres no pattern there at all.

With Linux, you can install patches immediately if there is a need, or later once they have had some good testing if there is not an immediate need. With Microsoft, you may install them when they say you may install them.

So, I can install a patch when its been released or later on if I decide ... in either of your cases? Wow, thats some industrial strength spin you have there!

Re:Linux patches?

[metallic]

I think they call that RHEL 5.

Re:Linux patches?

[trifish]

The sole problem is, and the OP rightfully criticized it, was that Slashdot never posts articles like "10 security flaws in Linux patched". Everytime Windows is patched, there's an article. Occassionally this is true for OS X. That's the point. Still seeno bias? C'mon it's Slashdot and we know how it goes here.

Re:Linux patches?

[darkwhite]

The problem is not simply insufficient attention by developers, and buffer overflow bugs can sometimes be very non-trivial. The big, ubiquitous lapse in security these days is the lack of sandboxing. Why are applications not sandboxed properly? Why, despite the full availability of the security framework to do it, are desktop applications allowed by default to read and write anywhere in the user's home directory, registry, communicate with everything, display anything they want on the screen, use any peripherals and communicate on the network in any way short of running a server? That's what's not acceptable. An obscure vulnerability in a big application might be excusable if it crashes it and causes it to nuke its config files, but it's very inexcusable if it installs spyware that steals the user's data or craps all over the user's home directory.

Re:Linux patches?

[PixieDust]

Agreed, which is pretty much the same thing I'm saying. The Buffer overflow bit was just an example. But you can see this everywhere. You see it in ACLs in firewalls, routers, and switches. You see it in applications that let everything just go willy nilly. You see it in default installations of some OSes. You see it in the installations of applications, in websites, email-clients, hell even games. And before you say "What could POSSIBLY happen in a game that could be a security threat?" Let me illustrate this example...

Take a well known game, say, a first person shooter based in WW-II. Fairly good game, kinda fun. Let's say it's released witha BIG following, and several expansions are released for it. Now imagine, that since it's initial release, it has had a vulnerability just hiding, waiting to be discovered. It is discovered, by a couple of gamers just having fun. Say there's a voting system (for kicks, map change, etc.). Let's say people use this voting system all the time to talk to people who are still alive, because it displays the vote in yellow text to everyone. Some ingenious players discover that if your vote is for a map change, and you manually enter the command and name via console something like:

callvote change_map "Shotgunner camping in the vent!!"

It's been a while so forgive the syntax if it's wrong. In any case, these intrepid gamer friends are having fun, and annoying each other with vote requests that mean nothing, and just fill the screen with yellow text (repeating gibberish to flood the screen so the player can't see). Let's say during this, both game clients crash. Hmm, well that sucks. So you go back to having fun, the server is running on an actual server in the garage so it's no biggy. Same thing happens again. The clients just crash immediately after a vote is called that is an absurd length. Hmmmm.. You get another friend involved, they join, they also crash. Interesting. Then you crash 2 clients, and have the 3rd join immediately after to see people running in place, stuck in doors, etc. Server is still running just fine. Clients however, have crashed. Now intensely curious, you start digging, and find the exact point at which is goes from "Annoying Spam Vote" to Buffer Overflow.

Now through various methods you discover that this vulnerability is definitely client specific. The server is totally unaffected. The server simply hands everything off to the clienhts, which don't know what to make of it, stuff is outside the buffer, client craps all over itself. Now someone malicious enough could take that, and create something that would quite literally be capable of hijacking any machine the game client was running on, and the only thing the user would notice MIGHT be a game crash (hell if you do it right you might be able to do it without the game itself crashing), which happens occasionally anyway, so it's ignored. Now let's say you notify the producer of this Entertainingly Amazing game, and exchange a few emails with them. 4 patches later it still isn't fixed. Several expansions later it still is not fixed.

Unacceptable. Absolutely unacceptable. And this happens throughout the industry. THAT is why security problems, are as much of a thorn in our side as they are.

*flips two coins onto the table, returns the soapbox to it's upright and locked position, and returns to her regularly scheduled nonsense*

/rant off

Re:Linux patches?

[T23M]

Completely agreed. While I sometimes use - and have respect for - Linux, I use Vista at home. Aside from a few driver glitches (nVidia's 8800 ForceWare, which is their fault, not MS'), it works fine for day-to-day browsing/gaming/what-have-you.

Unfortunately, when you're a college student among fellow geeks, word gets around that you not only USE Vista, but paid for and ENJOY it. This semester, I've had a couple of Linux fanboys (I hate using that word) railing me on what a bad OS Vista is.

Invariably, they bring up how annoying UAC is...and they don't seem to make the connection that it's just. like. sudo. On the off chance that they DO, in comes the snipe about how MS stole the idea from Linux (and stole the idea of a pretty desktop from OSX).

Maybe it's because we all said *random OS* was better than Windows because of those things? If you were in charge of the 800-pound gorilla, and the chimps next to him were getting too smart, wouldn't you teach him some new tricks?

I'm probably rambling by this point, but regarding the story's bias...you've got to admit, "flaw" is significantly more loaded (and less accurate) than "vulnerability".

Re:Linux patches?

[grcumb]

When are we going to start seeing regular Slashdot postings outlining Linux or other free software security patch releases in the same accusatory tone that the monthly Microsoft security bulletin releases bring? No, I'm not trolling, but I'm getting sick of the clear bias Slashdot editors (and most readers) have when it comes to matters of Microsoft.

No one's going to see this, and if they do it'll get modded down. But I'll feel better when I'm done.

You, sir, are a liar.

You complain about an accusatory tone, and when pressed to provide evidence, you admit that this advisory is actually perfectly neutral in its tone.

It makes me sick to see this kind of perverse logic through which one's critical faculties can be so twisted that even to make observations of fact and to draw logical, rational conclusions from them (e.g. Microsoft's security sucks) is somehow morally wrong.

Well I for one reserve the right to shit on whoever damn well deserves it. When Ubuntu releases a kernel patch that breaks an entire class of processor, or breaks X for a large number of their clients, I call them stupid. When Netscape broke the HTML standards and went cowboying around the Web with their 'Best Viewed With Netscape' logos, I shat on them as well. When WordPerfect made a perfect clusterfuck out of what was once the best piece of office software in the business, I castigated them for it, too.

But no company in the history of computing has ever been so deserving of our derision as Microsoft. Their business practices have caused me headaches and lost hours beyond count. In 2003-4 I did a rough estimate of the amount of time I lost to virus/trojan/spyware infested desktops. It was between 30 and 40% of my time. I moved all my clients to non-Microsoft applications for anything that touched the Internet, and my support time devoted to malware dropped to between 5 and 10%.

So when Microsoft releases 19 critical patches, do I consider it news? Damn straight. Am I inclined to be skeptical about these patches, to wonder what they're not telling me, what 'hidden treasures' might be included? Yes, and when I find that they disable my supported settings and re-enable that clusterfuck of a web browser IE for no good reason, do I get pissed off? Yes, I do.

And now you want me to cut MS some slack, because of bias? Let me tell you something, sonny Jim: Microsoft has earned this bias the hard way. I worked professionally on MS OSes for 9 long years before I finally gave up on them. If you can't see the purpose of critical appraisal and rational reaction, if you simply want to sit around the IT campfire singing Kumbaya and be nice even when somebody shits in your food, go ahead. But you and your astroturfing colleagues can leave me the hell out of it.

Working in IT is all about having a critical eye, and knowing when someone is trying to sell you code that more resembles a flaming bag of shit than anything else. It's obvious to me that you haven't yet mastered that art. So with all due respect, kindly sit down, shut up and learn to reason before you start shooting your mouth off again.

HTH HAND.

Changes Default Browser

[Anonymous Coward]

I used Microsoft Update to download and install the new patches last night. Lo and behold, upon reboot, Mozilla Firefox was no longer my default browser. It appears one of the new patches resets Internet Explorer as the default browser. Easy enough to fix, but why would a patch change a system's default browser in the first place?

Re:Changes Default Browser

[Kandenshi]

Happened to me as well, which was ... confusing.

Then I adjusted my thinking to Microsoft's point of view and tried to figure it out.

Now that IE7 is patched, it's much more secure than Firefox could ever be! Changing IE7 back to default is much like a firewall, an ounce of prevention is worth a pound of cure eh? By trying to get us back using IE7 they're just trying to prevent all the malware from getting on our systems, much like most of the rest of the patches.

It's a bit screwy, but that's the best rationalization I could come up with, anyone got a better one?

Cumulative IE 7 update 34,70 MB??

[edgrale]

What's up with the cumulative IE 7 update being 34,70 MB?
It is bigger than the x64 bit version!

Update also makes IE 7 the default browser

[edgrale]

Uh...

Did they even QA this thing? The size is huge and now it also stole the default browser setting.

Is this even news?

[anss123]

MS throws out a bunch of patches every month, and have been at it for years. It must be a regular event by now, right?

Cure the disease and lose the patient

[CyberVenom]

When Microsoft releases "critical" patches like this, one of the primary motivations for users, home and business alike to apply the patches is fear of loss of data if their computer falls victim to one of the new exploits. To "help" users keep their systems up to date, Microsoft has provided the Automatic Update tool. Formerly this tool would insistently prompt the user to reboot once updates had been installed. Recently, however, the tool has taken to rebooting computers of its own volition if it is unable to elicit a user response to its prompting within 5 minutes. What's the big deal? Well, lets say you have just typed up a nice email but want to add a couple more points to it before sending it off, but you have to walk away from the computer for a while. (coffee break, etc.) And when you come back 6 minutes later you find that Windows has terminated all your open programs, lost your email, rebooted, and is now happily chiding away to itself in a little speech bubble about some new updates having been installed. Well, that's fine - install your damn updates, but either do it without destroying my work or wait until I give you permission!
(yes, I lost an email I was writing last night because of this and I'm still a bit sore...)

Re:Cure the disease and lose the patient

[mattpalmer1086]

During the OS install, you are specifically asked to configure automatic updates. Some of the service pack installs also ask you to do this. [...] If the user decides to just click away the dialog asking you to configure automatic updates (which many OEMs will leave for you) then that's their damage.

Hmmm.. like most people, windows was preinstalled on my machine. If enabling a feature can lose the vital work of the user, it should not be a default. Also, a clear warning of the consequences should be made. In actual fact, I intentionally enabled the automatic update and I still didn't know what I was letting myself in for. My bad, I guess, but I never thought for one moment that enabling it like this might just cause my machine to lose my work while I was sitting in front of it, never mind if I popped out for a coffee! It fails the principle of least surprise.

I think that for most people, computers are tools, not objects of intrinsic interest in themselves. Any boring software (ie - stuff that should just work and not get in the user's way unless absolutely necessary) should do just that: just work. If can't just work, at the very least it should not endanger the user's work if at all possible.

Funnily enough, the argument that linux is harder to configure than windows is often made, but in my recent experience, I have to tinker less with linux than I ever did with windows, and I feel much safer!

Did they fix the cltreq.asp query nonsense?

[Medievalist]

People running Apache are starting to see this junk in their logs:

GET /_vti_bin/owssvr.dll?UL=1&ACT=4&BUILD=2614&STRMVER =4&CAPREQ=0 HTTP/1.1
GET /MSOffice/cltreq.asp?UL=1&ACT=4&BUILD=2614&STRMVER =4&CAPREQ=0 HTTP/1.1 This noise gets spewed at websites by IE if you load the latest version of Microsoft Office and turn on the discussion bar "feature".

You'd think sending these GETS to every single web site visited would be unnecessary (since IE can tell if it's connected to IIS, and only IIS is going to have cltreq.asp installed).

I'm guessing they didn't fix that one?

Re:Did they fix the cltreq.asp query nonsense?

[drinkypoo]

You'd think sending these GETS to every single web site visited would be unnecessary (since IE can tell if it's connected to IIS, and only IIS is going to have cltreq.asp installed).

Is there any reason someone with Chilisoft ASP couldn't implement the same functionality?

Re:Did they fix the cltreq.asp query nonsense?

[rthille]

Just create a symlink to /dev/urandom

dominant Internet Explorer.. my ass

[gd23ka]

Here, this is probably the article you had in mind:

"Microsoft has just released seven dominance advisories -- all rated critical -- with dominance enhancements for at least 19 dominance threats affecting the world's premier and most popular Windows(R) operating system, the widely deployed superior Office productivity suite and the most dominant Internet Explorer browser. Six of the 19 dominance threats affect Microsoft's latest and most exciting offering, the Windows Vista Operating System. 'There are dominance enhancements for 7 different domination points that could otherwise lead to unplanned code execution in the most popular word processor of all times Word, the most powerful spreadsheet application Excel and of course spectacular Office. Users of Microsoft Exchange the kick-ass central hub of Information Technology are also urged to pay attention to all of the critical bulletins, which cover 4 different dominance features. A cumulative IE dominance update addresses six potentially cool features. There are the six that apply to the dominant IE 7 on the hugely popular Windows Vista Operating System. The last bulletin in this month's batch apples to the widely acclaimed CAPICOM (Cryptographic API Component Object Model) and could also put users at risk of complete system dominance violations.'"

Why didn't they find these holes earlier?

[644bd346996]

Ok, here's what's bugging me: 6 out of 19 holes are still present in Vista. That means that, in developing Vista, they removed at least 13 holes. My question: was that an accident? If those 13 holes were identified as critical vulnerabilities during Vista development and fixed, then they should have been patched in XP too. If they were accidentally fixed by more broad changes in Vista, then I guess you can see that as good, but it still calls into question MS's ability to audit code.

On the other hand, if the rewritten portions of Vista removed 70% of the critical holes, that's pretty good. They might have been working on the right modules.

Re:Why didn't they find these holes earlier?

[MeBot]

More likely they're just issues that were mitigated as a side effect of the overall increased security in Vista. That's why minimizing attack surfaces is good even if you don't know of any vulnerabilities (yet). You also see similar patterns in new vulnerabilities between 2000 and XP SP 2. So it wasn't an accident even though they weren't aware of the vulnerabilities at the time.

Re:Why didn't they find these holes earlier?

[Samhain]

And if you read the about the patches you would notice that many of those 13 holes were with other products such as about 3 or 4 dealing with Office, some with Exchange, and some with windows DNS. These may or may not apply to Vista depending on what software you have installed on it.

Although I really hope someone is not trying to run Exchange on Vista. *grins*

Summary was incorrect

[SEMW]

Actually, the summary was incorrect regarding Vista: at least one of the vulnerabilities in question ("Uninitialized Memory Corruption Vulnerability CVE-2007-0944") is not present in Vista, and contrary to the summary's implication, only two out of the Vista vulnerabilities (CVE-2007-0945 and CVE-2007-2221) are rated critical.

Not, of course, that this excuses MS in any way (two is still two too many), but the summary was still rather misleading.

Re:No flaws in Vista itself, all 6 in IE7

[aichpvee]

I'm calling bullshit. Microsoft has been saying for 10 years that IE is INSEPARABLE from Windows. Any flaw in IE is a flaw in Windows. Because either you believe Microsoft or you stop your cheerleading and admit that Bill Gates and all the other execs at Microsoft are liars and that the feds should have broken the company up into a hundred little Microsofts.

That's the thing about revolution: it revolves!

[symbolset]

So you work for the New AT&T then?

Only One of the Vista Bugs was "Critical"

[ThinkFr33ly]

Only 1 of the 6 bugs that affected Vista was rated "critical". (Critical is typically reserved for bugs that could allow somebody to remotely take over the machine.)

In the case of the one bug that was rated critical, the rating was dependent on several mitigating factors, including that the user running as full admin with UAC turned off. (Obviously not the default configuration.)

Only in that scenario could the machine be compromised, and even then the successful execution of exploit code was unlikely thanks to ASLR and various other security measures. It was far more likely to simply cause a browser crash.

Considering Vista has been out since November of last year, its security record so far as been extremely impressive.

Which is more of a threat?

[thedbtree]

I don't mean to troll and I'm not necessarily disagreeing with you about a bias, but I tend to think of Microsoft vulnerabilities and patches to be more important than the Linux counterpart.

It's not my intention to imply Linux has fewer security bugs/holes/etc, because I haven't done any research in that regard.

What I am saying is that Microsoft dominates the market; so therefore a Microsoft vulnerability and patch are more newsworthy in than a more obscure piece of software, in my book. I'm not talking about "quality" of a vulnerability in terms of criticality, I'm talking about the quantity of systems around the globe that will be affected by articles said 19 "flaws".

Once again, no research here, I realize there are probably many more *nix systems out there than I realize, but if I walk down my street and ask every neighbor what they're running, I can almost assure the majority are running Windows.

Re:No flaws in Vista itself, all 6 in IE7

[sid0]

I'm calling bullshit.

On what? That IE7 was developed independently of Vista?

Of course it was developed independently. It was released long before Vista was.

Microsoft has been saying for 10 years that IE is INSEPARABLE from Windows.

They are correct in a sense.

While IE can be removed from Windows XP (I'm not sure about Vista) using XPlite, doing so breaks a lot of other things in Windows (help files etc). Trust me, I've tried it.

Any flaw in IE is a flaw in Windows.

I can see the argument for it, although I'll disagree. When I say "Vista" I mean the kernel + the subsystems (graphics, audio, network etc) + the security layer (UAC, digital signatures). The internet browser bundled with the OS -- especially when it is made available for another couple of OSes, and the development team is not part of the Vista development team -- doesn't count as part of the OS.

Plus, you have the choice of browser. You do not have the choice of subsystem or kernel.

The help files are non-essential stuff, so you can technically use Vista or XP without ever seeing IE. I cannot say the same for the other things.

Re:No flaws in Vista itself, all 6 in IE7

[ad0gg]

You can't seperate IE from windows. It will break the windows help system which uses the IE renderer. It will break apps that depend on the IE engine(about boxes use this a lot with HTML/ActiveX that hooks into application). Removing IE Engine from windows would be like removing konqueror(really the KHTML engine) from KDE.

System restart

[D H NG]

I've had it up to here with Microsoft's automatic restart after a system update. Last night somebody was sending me a 1 GB file via Skype. It was halfway done when I went to bed. In the morning, my computer had restarted. All the transferred data was lost. As soon as I get my wireless card working in Ubuntu, I'm gonna wean off Windows forever.

Vista patches

[obeythefist]

The vista patches are all just to disable the one-click activation hacks that are circulating.