We usually don't report on security flaws, unless they're on platforms that usually don't see such flaws, or when the flaw in question is pretty serious. Well, a new zero-day flaw has been discovered in Windows Vista and Windows 7 which will trigger a blue screen of death using the new SMB 2.0 protocol. Update: Windows 7 RTM and Windows Server 2008 R2 are not affected by the flaw. So, this is less of a problem than expected.
Post a Comment
Member since:
2005-11-13
Member since:
2006-05-10
Member since:2006-12-05
*puzzled stare*
http://macdailynews.com/index.php/weblog/comments/22329/
Second image down. :p
Member since:
2006-04-03
Member since:2009-09-08
Member since:2007-06-12
it doesn't matter, it's too late for Microsoft to patch any of this. they've already labeled and sent off their build as RTM. that doesn't stop them from releasing a windows update, which i assume will be pretty fast.
Member since:
2009-09-08
I saw this exploit and went "LOLWUT?"
I tried it on the Group Policy "Windows" guy's lab systems who work next to me and watched 5 VM's BSOD.. I ROFL'ED... R . O . F . L 'ed sir.
Way to go Microsoft... I wonder if Windows 2008 suffers from this also.
I have a sudden urge to go into #microsoft in IRC and start blasting that python script at people
Member since:2005-07-06
That would likely be ineffective since neither Vista nor 7 allow SMB traffic from public networks by default. This attack would likely be limited to LANs or misconfigured systems.
As a followup, this flaw could provide incentive to avoid (or double-check) leaked/torrented builds as it's pretty easy to create a modified image that allowed SMB through the firewall by default. A naive user may think their downloaded build has the same security as the official distribution.
Edited 2009-09-09 00:51 UTC
Member since:2005-07-06
Member since:
2009-09-09
Although both Vista and Windows 7 may share the same SMB. According to Microsoft Security Response Center:
"Our investigation has shown that Windows Vista, Windows Server 2008 and Windows 7 RC are affected by this vulnerability. Windows 7 RTM, Windows Server 2008 R2, Windows XP and Windows 2000 are not affected by this vulnerability"."
Source:
http://blogs.technet.com/msrc/archive/2009/09/08/microsoft-security...
---
and did OSnews check if its working on Windows 7 all versions as you say RTM or not? Since even heise security, a security research firm says it had no apparent effect on Windows 7:
http://www.h-online.com/security/Hole-in-Windows-Vista-and-7-allows...
Please check.
Member since:
2005-11-09
Member since:
2008-05-26
This flaw doesn't really matter. It's not a schoolboy programming error. It's not a ridiculously bad architectural design. The timing is somewhat awkward, but the patch will come through in the first Windows 7 updates, and most businesses won't switch to Win 7 until Service Pack 1 (or they will stick with XP until kingdom come).
Member since:
2008-01-05
Member since:2008-01-05
Member since:
2009-09-09
Member since:2005-06-29
Member since:
2006-07-04
Member since:
2007-08-17
>> Update: Windows 7 RTM and Windows Server 2008 R2 are not affected by the flaw. So, this is less of a problem than expected.
So it only effects recent MS desktop operating systems which are available to the general public? Thank goodness for that, you had me worried for a moment.
Member since:
2008-03-10
Test your code against RTM and see if it works. I haven't done so yet. But after seeing the notepad awesomeness and now SMB.. I think that Adobe/CA(Computer Associates) can rest assured that they will never have the most crappy software design.
I leave you guys with some ASM code to test out. This is not a BSOD issue, it's a Remote Exploit. A hax0r can take over your machine, so it's a bit more than just making it unavailable.. I smell botnets!!!
http://www.reversemode.com/index.php?option=com_mamblog&Itemid=15&t...
Member since:2006-01-02
Member since:2008-10-30
Member since:2006-01-02
Member since:
2005-07-12
