SMBLoris attack proof of concept: brings down my fully patched Win10 box in seconds. https://gist.github.com/marcan/6a2d14b0e3eaa5de1795a763fb58641e …pic.twitter.com/tJWYiXRP7z
-
-
Replying to @marcan42
And this was slowed down by having Wireshark running in the background. It's twice as fast or more after killing that.
2 replies 6 retweets 22 likes -
Replying to @marcan42
Win10 gone in under 10 sec of SMBLoris (8GB RAM). Less overhead on the attacker side this time. Stopping the attack causes borked graphics.pic.twitter.com/h4n6hbxnIA
2 replies 54 retweets 106 likes -
Replying to @marcan42
The graphics thing seems like GDI handle exhaustion to me.
1 reply 0 retweets 0 likes -
Maybe, but as someone who often runs Windows under memory pressure, I've seen all sorts of weird graphics drivers issues when near the line
1 reply 0 retweets 1 like -
Replying to @marksteward @gibbed
Running the attack for a bit longer causes disk I/O errors due to the storage driver not being able to allocate, and then everything borks.
1 reply 0 retweets 2 likes
The system looks like it recovers but it keeps freezing periodically, things stop working, and the only fix is a hard reboot.
-
-
Replying to @marcan42 @marksteward
I guess if memory was exhausted in general GDI handle allocation would fail too. Pretty nasty.
0 replies 0 retweets 1 likeThanks. Twitter will use this to make your timeline better. UndoUndo
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.