Microsoft Takes 7 Years to Fix Security Exploit

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
I think this is some kind of record, isn’t it? If not, it should be. ;)

That means that a known security vulnerability related to a Microsoft authentication protocol sat on your Windows box for more than seven years, waiting for Microsoft to get around to fixing it: This vulnerability allows an attacker to redirect an incoming SMB connection back to the machine it came from and then access the victim machine using the victim's own credentials. (Hence the term "credential reflection").
 
This is kind of turn-around time from a multi-billion dollar company is unacceptable. Who knows how many people were victimized by this exploit.

Basically we pay millions of dollars for poorly patched products.. :(
 
Lets all panic. Microsoft spend millions of dollars fixing software that people have already purchased, for free. Yet somehow out of several thousand security holes they have fixed, one really low threat issue was missed for several years. Horrible decision by Microsoft, how dare they wait so long to patch a hole it seemed no one ever used. How long must we be tortured by using such insecure O/S, one that billions of people use, one that if even 1% of the people using it found a security hole, that would 10 million holes will be found. Why can't we use another O/S like OSx where only ~100 million people use it? Chances of anywhere as many holes being found would be a whole lot less likely.
 
Hmm... does that mean it's time to get the pitchforks and torches ready for the upcoming angry mob riot? :eek:

... :cool:
 
PC World article said:
This type of attack would be blocked by a firewall*, so a hacker would have to already be on a computer within the network in order to launch the SMB relay. Microsoft rates the flaw as "important" for Windows XP, 2000 and Server 2003 users, and as "moderate" for Vista and Server 2008.
*Unless you have TCP ports 139 and 445 enabled at your router, it's not a big problem for most people. You would already have to be hacked to attack other computers on your network using this exploit. From MS06-068: "Users whose accounts are configured to have fewer user rights on the system could be less impacted than users who operate with administrative user rights."

On the plus side, Win98 and WinME are unaffected. ;)
 
I am sure the priority was low because the threat level was low.

Severity Rating for W2k SP4, XP, 2003 - IMPORTANT not low


It is an importnant fix for a low threat. I agree with riot8ap to some point.

This bug could only be used by somebody on your network. The article itself stated how it would not work through a firewall. If that means any firewall (hardware or software) then maybe the windows firewall alone was enough to stop it. So that leaves you with only windows 2000 machines that you need to worry about. Lets assume that the windows firewall wasn't enough. They still have to get physical access to your network, plug into it and then send you an email and get you to click on a link to use this. So then you are looking at the person needing to know the email addresses of people in your company.

So that means in order for this to be a valid threat a person would have to get a list of email addresses, physically break into a building and hide somewhere, plug into the network, send out emails to a few people in hopes that some of them click on the link, steal your password and gains access to your machine, do what ever he wants to do (while still hiding), then leave.

Little chance of that happening. If they do manage to do all that then you have other security problems you need to deal with.

Overall, for any decent network, this flaw could really only be used by an employee or somebody else on the inside that is already on your network that wants to gain access to stuff they shouldn't have access to or that wants to mess stuff up.

So in that regards I have to agree that overall it is a pretty low threat, but if it did somehow managed to get taken advantage of then it would be a problem (hense why it was listed as important). However even if it was a low threat, I still think that they should have probably went ahead and fixed it sooner just to get it taken care of.
 
Is it not a good sign that they are getting around to bugs that have been bumped until now?
 
This is kind of turn-around time from a multi-billion dollar company is unacceptable.

The reasons MS is no longer trustworthy are too many to list, so the only thing surprising about this alleged fix is that they bothered at all.
 
Is it not a good sign that they are getting around to bugs that have been bumped until now?

I guess that is one way to look at it. They have gotten all the current major problems fixed and are now left with stuff they have been putting off for years due to having other more important ones to fix.
 
This is kind of turn-around time from a multi-billion dollar company is unacceptable. Who knows how many people were victimized by this exploit.

Basically we pay millions of dollars for poorly patched products.. :(

Amusingly, a bug was recently fixed in OpenBSD that was 25 years old.


This is kind of turn-around time from an open source project is unacceptable. Who knows how many people were victimized by this exploit.

Basically we pay nothing for poorly patched products.. :(
 
It is an importnant fix for a low threat. I agree with riot8ap to some point.

This bug could only be used by somebody on your network. The article itself stated how it would not work through a firewall. If that means any firewall (hardware or software) then maybe the windows firewall alone was enough to stop it. So that leaves you with only windows 2000 machines that you need to worry about. Lets assume that the windows firewall wasn't enough. They still have to get physical access to your network, plug into it and then send you an email and get you to click on a link to use this. So then you are looking at the person needing to know the email addresses of people in your company.

So that means in order for this to be a valid threat a person would have to get a list of email addresses, physically break into a building and hide somewhere, plug into the network, send out emails to a few people in hopes that some of them click on the link, steal your password and gains access to your machine, do what ever he wants to do (while still hiding), then leave.

Little chance of that happening. If they do manage to do all that then you have other security problems you need to deal with.

Overall, for any decent network, this flaw could really only be used by an employee or somebody else on the inside that is already on your network that wants to gain access to stuff they shouldn't have access to or that wants to mess stuff up.

So in that regards I have to agree that overall it is a pretty low threat, but if it did somehow managed to get taken advantage of then it would be a problem (hense why it was listed as important). However even if it was a low threat, I still think that they should have probably went ahead and fixed it sooner just to get it taken care of.

Yeah, but for me, a threat is a threat. Low, high: Don't need em'. Although thinking a human would have to do all what you said would be necessary, never underestimate the programmer. Bots can be just as bad, if not worse than a human in action. That situation would be much worse if there are computers networked with different firewalls/security software. That's my, uhmm.. Theory.
 
//[T.0.P]//;1033305212 said:
Yeah, but for me, a threat is a threat. Low, high: Don't need em'. Although thinking a human would have to do all what you said would be necessary, never underestimate the programmer. Bots can be just as bad, if not worse than a human in action. That situation would be much worse if there are computers networked with different firewalls/security software. That's my, uhmm.. Theory.

The problem with that though is that if you have a bot then your machine is already compromized and they can already get your password by many other methods.

Although if Microsoft has to choose to spend time fixing low level or fixing high level. I'd rather they fix the high level ones first. However I do agree that all both low and high need to be fixed. But at the end of the day, I think it is better to fix the flaws that are eaiser to take advantage of and can cause the most trouble before trying to fix things that are harder to take advantage of. That way you can keep the most people as safe as possible.

Another thing to realize is that Microsoft isn't the only one that does stuff like this. A lot of companies rate bugs and fix the higher ranked ones first. Remember when the bug list for Firefox was released before v3 was released and there were a lot of low ranked bugs from v1 that were not fixed and were not planned to fixed for some time.
 
This is nothing compared to how long it took them to fix Windows 95... :p
 
Back
Top