Windows 7 Unaffected By Zero-Day Flaw

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
According to this security advisory, reports of a zero-day flaw that supposedly affected Windows 7 are not true. The final version of Microsoft's latest OS is not vulnerable to the attacks, everyone can calm down.

Microsoft is investigating new public reports of a possible vulnerability in Microsoft Server Message Block (SMB) implementation. We are not aware of attacks that try to use the reported vulnerabilities or of customer impact at this time. We are actively working with partners in our Microsoft Active Protections Program (MAPP) to provide information that they can use to provide broader protections to customers.
 
Just to be clear, Vista and Server 2008 are still in trouble. Brought down a machine with a simple python script.
 
As noted in the other thread (because the advisory is currently down, just checked it again):

Vista x86 and x64, and Windows Server x86 and x64 (and the Itanium version) are affected.

No other versions of Windows are affected, including Server 2008 R2 x64. Just the 4 versions listed above are affected...
 
As noted in the other thread (because the advisory is currently down, just checked it again):

Vista x86 and x64, and Windows Server x86 and x64 (and the Itanium version) are affected.

No other versions of Windows are affected, including Server 2008 R2 x64. Just the 4 versions listed above are affected...

Well that lets out XP Pro(x32), XP Pro x64 and Win7 as the title says. :D
 
Well this should hope dispell the myth that Win7 is just Win-Vista-SP3
 
Actually, unless the SMB2 driver was a memory leaks or bloat or inefficient CPU use, I wouldn't have minded if they'd left it alone.
 
In reading Microsoft's bulliten, they are saying that the guy that posted this flaw DIDN'T contact Microsoft properly. He said he did and made his finding public only after Microsoft didn't respond he said.
 
I guess that qualifies as 'attempted responsible disclosure'. :rolleyes:

I think that only thing that qualifies him for is an idiot. Good find on his part but he should have made sure that Microsoft got his message before ragging on them and releasing this. But my guess this shouldn't be that hard to fix if its already been fixed in 7.

Also I do take a little exception in that "this should have been caught." No shit Sherlock. It still took THREE years to find.
 
I just had a Windows 7 RTM box get hit with this.

I was using the computer when it suddenly froze up. I reboot the machine, and the safemode menu pops up and the cursor selection started moving on its own! I reset the machine, and the same thing happened... someone was trying to go into safemode. I shut the machine down, pulled the network cable, and it booted up normally.

Went into the firewall settings, blocked port 445, and plugged the network cable back in. So far so good.
 
I just had a Windows 7 RTM box get hit with this.

I was using the computer when it suddenly froze up. I reboot the machine, and the safemode menu pops up and the cursor selection started moving on its own! I reset the machine, and the same thing happened... someone was trying to go into safemode. I shut the machine down, pulled the network cable, and it booted up normally.

Went into the firewall settings, blocked port 445, and plugged the network cable back in. So far so good.

Sorry if I have a hard time believing you but you'd be the first person to see this on Windows 7 and Microsoft has already stated that this doesn't affect 7. So you have to understand that it's hard to believe that your problem in 7 was caused by this flaw.
 
1. Who says I'm the first?
2. If MS told you that filling your computer with Cheese Whiz would properly secure it from any exploit, would you go out and buy some Cheese Whiz? Wouldn't be the first time they lied/made a mistake trying to cover their own asses.
3. Hackers don't just say "darn, I guess I'll stop trying to use that exploit" whenever a fix is released. They adapt.

I'm not saying you're wrong and I'm right, but it seems awfully convenient that a computer exhibits the same characteristics of an exploit that was just reported... I'm certainly open to an alternative explanation why a Windows 7 machine with a fresh install suddenly crashes and starts controlling itself on reboot.

*checks computer for gnomes*
 
I should have been the more accurate, you'd be the first person that I'VE heard that says they saw this on Windows 7. As far as Microsoft, they have PUBLICLY said that this didn't affect 7. If indeed they are wrong they'd look pretty stupid and its been confirmed independently so its not just their word I'm taking.

Did you see any port 445 traffic?
 
*sigh*, my boss has a router with dd-wrt installed, and doesn't have logging turned on. Useless.
 
I have been working with the beta for Win7 for over 5 months now, i have 5 variaitions currently on the lab machines one of which is the final, all are vun to this script - Microsoft obviously are making a patch, stating that Win7 is not vun is bull...





"Want a [H]ard OS? Built it yourself ... Gentoo ..."
 
Back
Top