Slashdot Mirror
Zero-Day Windows Security Flaw Can Crash Systems, Cause BSODs (helpnetsecurity.com)
Orome1 quotes a report from Help Net Security: A zero-day bug affecting Windows 10, 8.1, Windows Server 2012 and 2016 can be exploited to crash a vulnerable system and possibly even to compromise it. It is a memory corruption bug in the handling of SMB traffic that could be easily exploited by forcing a Windows system to connect to a malicious SMB share. Tricking a user to connect to such a server should be an easy feat if clever social engineering is employed. The vulnerability was discovered by a researcher that goes by PythonResponder on Twitter, and who published proof-of-exploit code for it on GitHub on Wednesday. The researcher says that he shared knowledge of the flaw with Microsoft, and claims that "they had a patch ready 3 months ago but decided to push it back." Supposedly, the patch will be released next Tuesday. The PoC exploit has been tested by SANS ISC CTO Johannes Ullrich, and works on a fully patched Windows 10. "To be vulnerable, a client needs to support SMBv3, which was introduced in Windows 8 for clients and Windows 2012 on servers," he noted, and added that "it isn't clear if this is exploitable beyond a denial of service." Until a patch is released, administrators can prevent it from being exploited by blocking outbound SMB connections (TCP ports 139 and 445, UDP ports 137 and 138) from the local network to the WAN, as advised by CERT/CC. "The tweet originally announcing this issue stated that Windows 2012 and 2016 is vulnerable," the researcher said. "I tested it with a fully patched Windows 10, and it got an immediate blue screen of death."
didn't they change it to a green screen?
Unless there's a PoC that demonstrates remote code execution, this isn't really newsworthy.
Ha! Joke's on you! I'm still running SMBv1 with NTLMv1!
sry, been drinkin' since noon. *grin* game on all and be safe.
Yet another reason, if we really *need* another, to quit using MS products. I used/supported MS products for 20 years as a sysadmin, but when I retired in 2010, I decided I was done with Windows on my personal systems. I had been dualbooting Win7 and Linux, but once I made the decision, I simply deleted the Win7 partition, and reinstalled grub. After 6 years of zero MS, I've not missed it a bit.. In fact, I'm forced to use Windows in a part-time volunteer support position with a local charity, and I find that using Windows now, after being 100% Linux for going on 7 years, is very unnatural. After seeing all of the multiple forms of abuse MS heaps on those who still use Windows, I couldn't be happier with my decision...
THANK YOU, Edward Snowden!! Americans owe you a debt of gratitude (whether they know it or not..)
Crashing all day? I suggest getting a book or taking a class on how to install and configure 2012 servers. Or maybe just get someone who knows what the hell they are doing to setup your server(s). The #1 cause of server exploits in both Windows and Linux OS's are the idiot administrators.
No, on second thought let's not blame it on Trump. There's plenty else he correctly deserves the blame for, and Microsoft alone is responsible for the reputation and state of the OS software they provide. Software which while not perfect has nonetheless improved considerably over the years. They've made numerous mistakes along the way but as a UNIX Administrator with well over two decades of experience I can tell you their current product offering is considerably more stable, more usable and less vulnerable than it used to be. Anybody that remembers Windows 2.0, 3.1, 95, 98, ME and XP will no doubt have horror stories relating to feeling like Microsoft's crash test dummies. It hasn't stopped, but my personal experience is that it seems to happen less often than it used to.
If you have found someone stupid enough that you can socially engineer this way then you can get them to do something far worse without any need to exploit a bug. seems a pointless exploit at this point unless someone can work out a way to engineer a remote attack that doesn't involve user stupidity.
Attacking SMB is retarded. SMB services should -never- ever be exposed to the internet, under any circumstances. Anyone who does expose SMB to the internet deserves to get hacked. Bury that crap in a VPN, use a firewall, and disregard this silliness.
Those blue screens and the event viewer are probably trying to tell you something. You may want to look into it.
My bet is bad memory or some other faulty component or a bad driver.
Regardless of whether they pushed it back or not, if they're planning to release next Tuesday then disclosing the hole with PoC exploit code is just irresponsible. You could have waited 5 more days.
Hire a Linux system administrator, systems engineer,
" ... Windows ... Can Crash Systems, Cause BSODs "
FTFY
We usually have 9.1 crashes per day on our Windows servers, but today we had over three hundred. We have TCP port 139 open from our internal network to production, so maybe one of our employees has an infection. After closing that port about twenty minutes ago, there's only been a single Windows server that crashed. Glad I found this story.
Are people logged into those servers and browsing the web? This hole can be exploited if your network allows *outbound* traffic on ports 137/138/139/445. A malicious or compromised web page can embed a link like <img src="\\1.2.3.4\share$\exploit"> and now you're owned, even if inbound SMB is blocked.
I have an SMB server on my network and I think I just found a way to convince my family to switch to Linux.
(Score: -1, Stupid)
I would suggest looking in a mirror to find the issue then.
Yeahh, they trying to tell you about a segfault at address 0xdeadbeef in binary blob xyz, but sorry, you don't get to debug it. tough shit. keep the money flowing anyway, k?
CLI paste? paste.pr0.tips!
I didn't mean to imply all administrators are idiots. There are a lot of very good administrators out there but at the same time there are also a lot of not so good administrators.
"If a system/domain/network administrator needs a class or a book to setup a stable basic system, they are in the wrong line of work"
Maybe they are just entry level newbies that do need books and classes to supplement their real world experience.