Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Attacks/Breaches

2/3/2017
02:45 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Windows SMB Zero-Day Exploit On The Loose

Vulnerability allows remote attackers to trigger denial-of-service conditions on several Windows client versions.

US-CERT and other organizations Friday warned of a zero-day memory corruption bug in several versions of Microsoft Windows that could allow a remote attacker to cause a vulnerable system to crash and reboot.

Proof of concept code for exploiting the vulnerability has already been released on GitHub and is now publicly available for anyone to use. As of mid-day Eastern Time on Friday, no patch was available for the vulnerability, which poses more of threat for home and small businesses than enterprises.

The bug exists in the way certain Windows versions handle Server Message Block (SMB) traffic, Carnegie Mellon University’s CERT division said in an alert. By sending a specially crafted message from a malicious server, an attacker can trigger a buffer overflow condition in a vulnerable Windows system and cause it to crash, the alert noted. Several methods are available to attackers to get a Windows client system to connect to a malicious SMB server, sometimes with little to no user interaction, it added.

The Microsoft SMB file sharing protocol allows Windows clients to request services and to read and write files from Windows servers in a network. It has been the source of several security issues over the years.

A Microsoft spokesperson downplayed the severity of the issue. "Windows is the only platform with a customer commitment to investigate reported security issues, and proactively update impacted devices as soon as possible," the spokesperson said in a statement. "Our standard policy is that on issues of low risk, we remediate that risk via our current Update Tuesday schedule." 

Johannes Ullirch, head of the Internet Storm Center at the SANS Institute, said he tested the issue on a fully patched Windows 10 system using the proof of concept code and immediately got a blue screen of death. All Windows clients that support SMBv3 including Windows 2012 and 2016, appear vulnerable to the exploit, he said.

"The bug is a denial of service bug," Ullrich told Dark Reading. "If a system is hit by the exploit, then it will reboot." The bug does not appear to give attackers a way to execute code or do anything beyond triggering a denial of service condition.

Exploiting the vulnerability is easy, Ullrich says. The attacker can use the exploit to implement an SMBv3 server and then trick the victim into connecting to it. "The easiest way to accomplish this is by inserting a URL linking the server to a Web page," he says.

The URL might look like \\192.0.2.1\ipc$, where 192.0.2.1 is the IP address of the server. "An image tag like <img src=”[malicious url]”> will trigger the exploit."

The vulnerability is another reminder why it is necessary to block outbound SMB connections by blocking ports 445, 135 and 139, Ullrich says. "Many networks do not close these ports outbound, which opens up a number of attack possibilities, not just this one."

Home and small business users are more likely affected by the issue than enterprise users as small business and home firewalls usually do not block these connections by default, he notes.

In its advisory, CERT said it was currently unaware of a "practical solution" to the problem and urged organizations to block outbound SMB connections from the local network to the WAN on TCP ports 139 and 445 along with UDP ports 137 and 138.

Related Content:

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
A Realistic Threat Model for the Masses
Lysa Myers, Security Researcher, ESET,  10/9/2019
USB Drive Security Still Lags
Dark Reading Staff 10/9/2019
Virginia a Hot Spot For Cybersecurity Jobs
Jai Vijayan, Contributing Writer,  10/9/2019
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Current Issue
7 Threats & Disruptive Forces Changing the Face of Cybersecurity
This Dark Reading Tech Digest gives an in-depth look at the biggest emerging threats and disruptive forces that are changing the face of cybersecurity today.
Flash Poll
2019 Online Malware and Threats
2019 Online Malware and Threats
As cyberattacks become more frequent and more sophisticated, enterprise security teams are under unprecedented pressure to respond. Is your organization ready?
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2019-14832
PUBLISHED: 2019-10-15
A flaw was found in the Keycloak REST API before version 8.0.0 where it would permit user access from a realm the user was not configured. An authenticated attacker with knowledge of a user id could use this flaw to access unauthorized information or to carry out further attacks.
CVE-2017-10022
PUBLISHED: 2019-10-15
In haml versions prior to version 5.0.0.beta.2, when using user input to perform tasks on the server, characters like &lt; &gt; &quot; ' must be escaped properly. In this case, the ' character was missed. An attacker can manipulate the input to introduce additional attributes, potentially executing ...
CVE-2019-10759
PUBLISHED: 2019-10-15
safer-eval before 1.3.4 are vulnerable to Arbitrary Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code.
CVE-2019-10760
PUBLISHED: 2019-10-15
safer-eval before 1.3.2 are vulnerable to Arbitrary Code Execution. A payload using constructor properties can escape the sandbox and execute arbitrary code.
CVE-2019-17397
PUBLISHED: 2019-10-15
In the DoorDash application through 11.5.2 for Android, the username and password are stored in the log during authentication, and may be available to attackers via logcat.