Welcome Guest. | Log In | Register | Membership Benefits


Topics:   Evil Bytes : Insider Threat Tech Center : Vulnerability Management Tech Center

Metasploit Adds Exploit For Unpatched Windows SMBv2 Bug

The upcoming stable release of Metasploit Framework version 3.3 is brimming with awesome new features that will make a lot of penetration testers happy. New features include the ability to take screenshots of exploited systems, while others add raw power, like being able to exploit the unpatched SMBv2 vulnerability in Windows Vista and Server 2008.

Sep 28, 2009 | 06:43 PM | 

By John H. Sawyer
Dark Reading

The upcoming stable release of Metasploit Framework version 3.3 is brimming with awesome new features that will make a lot of penetration testers happy. New features include the ability to take screenshots of exploited systems, while others add raw power, like being able to exploit the unpatched SMBv2 vulnerability in Windows Vista and Server 2008.We've all heard the saying, "A picture is worth a thousand words," and in the world of penetration testing, that still holds true. There's nothing like being able to include in the final report a screenshot of the CEO's desktop while he was playing Solitaire, or a screenshot of the CFO's desktop with Excel open showing the monthly production numbers.

In Metasploit Framework version 3.3, a new feature of the Windows Meterpreter payload allows screenshots. While you may think that having the ability to take screenshots of a remote machine isn't a big deal, you'd be surprised about just how useful it can be; you never know what juicy info might be on-screen while you have access. One example I've heard was a pen test in which a network administrator's system was compromised and a spreadsheet was opened with IP addresses and passwords to all the network equipment. (I've never been quite that lucky.)

Something that HD Moore, founder of the Metasploit Project, mentions in his blog post this morning about the screenshot process is that meterpreter must be loaded in a process that has access to the active desktop such as "explore.exe." When I was testing earlier today, it was something I forgot about when exploiting a Windows 2008 server that had no logged on users -- there was no desktop to take a screenshot of. It worked fine, however, on a Windows Vista system with someone actively logged on.

Speaking of Windows 2008 Server, there is a new, highly anticipated exploit for the SMBv2 vulnerability that works on Windows Vista Service Pack 1 and 2, and Windows Server 2008 Service Pack 1 and 2. It works great and was the exploit tested when trying out the screenshot function above. It worked against both versions of Windows that are fully patched according to Microsoft Update, and I was able to get a remote command prompt on each.

I don't know about you, but I'm excited about the new SMBv2 exploit. Just 20 days after Microsoft issued Security Advisory 975497, there is an exploit in the free, open source Metasploit Framework that works like a charm. But you don't have anything to worry about, right? You're employing firewall rules that follow best practices by blocking inbound TCP port 135 and 445, which just happens to be one of the workarounds discussed in the Microsoft Security Advisory.

Think again. Remember my post about a client-side attack using Metasploit? Follow those exact same steps, but replace steps 3 to 5 with "Exploit MS Active Directory Domain Controller with SMBv2 Exploit," and you've got GAME OVER!

As HD said, "Voila! A great way to justify disabling SMB2 across your network." Now, get to rolling out the Group Policy to disable SMBv2 (if you haven't already).

Take a look at the Metasploit blog for more information about the new features and when the stable release will released. For those using the version within Subversion, many of the features are already there.

John H. Sawyer is a senior security engineer on the IT Security Team at the University of Florida. The views and opinions expressed in this blog are his own and do not represent the views and opinions of the UF IT Security Team or the University of Florida. When John's not fighting flaming, malware-infested machines or performing autopsies on blitzed boxes, he can usually be found hanging with his family, bouncing a baby on one knee and balancing a laptop on the other. Special to Dark Reading.



Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

Dark Reading encourages readers to engage in spirited, healthy debate, including taking us to task. However, Dark Reading moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. Dark Reading further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
Subscribe to RSS



Vulnerability Management Reports

report Choosing the Right Vulnerability Scanner for Your Organization
Vulnerability scanners can be used to help detect and fix systemic problems in an organization's security program and monitor the effectiveness of security controls. However, a vulnerability scanner can improve the organization?s security posture only when it is used as part of a vulnerability management program, in which products, processes and people are working together to find, identify, prioritize and mitigate threats. Here are some tips on choosing and implementing vulnerability scanners in your enterprise.

report Using Google to Find Vulnerabilities In Your IT Environment
Attackers are increasingly using a simple method for finding flaws in websites and applications: they Google them. Using Google code search, hackers can identify crucial vulnerabilities in application code strings, providing the entry point they need to break through application security. Sound scary? It is, but there is good news: You can use these same methods to find flaws before the bad guys do. In this special report, we outline methods for using search engines such as Google and Bing to identify vulnerabilities in your applications, systems and services--and to fix them before they can be exploited.

report Security Pro's Guide to Patch Management
It's no longer sufficient to patch just Windows, Office and IE. With the massive array of applications now residing on enterprise PCs, and the proliferation of mobile and cloud-based applications, your business is far too vulnerable to exploitation unless you have a solid strategy for patch prioritization, deployment and quality assurance. Follow these steps to put your plan in place.

Other reports from the Vulnerability Management Tech Center:




Featured Webcasts
Featured Whitepapers
Featured Reports