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.

Analytics

10/23/2006
09:10 AM
Connect Directly
Google+
Twitter
RSS
E-Mail
50%
50%

Metasploit to Go Wireless

Wireless device-driver software set to emerge as the next big petri dish for exploits, attacks

HD Moore, Jon Ellch (a.k.a. johnny cache), and another researcher known as "skape," are collaborating on adding 802.11 wireless exploits to the Metasploit 3.0 penetration testing tool. Moore, the creator of Metasploit, has written a wrapper for the tool that lets it execute raw 802.11 packet injection.

802.11 packet injection lets an attacker go after the lowest level of the operating system, such as wireless device drivers, which Ellch says are an attacker's goldmine. "This code is full of bugs because it is not written by software companies and until recently, bugs in it were not really exploitable," Ellch says. "Now that we can send packets at such a low level, we can hit the bugs in the code."

Wireless device-driver vulnerabilities are becoming a hot topic. Ellch, in a presentation at last week's Blue Hat summit, told Microsoft it needs to work with device-driver vendors to turn off some of the unnecessary wireless card features to minimize the risk of a hack. "The basic problem is end users have two choices on the driver, 'on' or 'off.'" And there's a lot of code in this software associated with features users may not need, such as "power-save," for instance, that leaves the door open for bugs.

"The more code you have, the more bugs there are," he says.

And with Metasploit 3.0 about to include 802.11 exploits as well, Microsoft and device-driver vendors may have to take action sooner, rather than later. "A working Metasploit module is definitely motivation for wireless vendors to review their code," says Moore, who is also director of security research with BreakingPoint Systems. Moore says the new features will likely be ready to go in the next few weeks for Metasploit 3.0.

Meanwhile, Ellch says for Microsoft to better secure the 802.11 device-driver layer of the kernel, it would have to determine which features users could disable in their device drivers. "Microsoft can't fix this themselves," though. The software giant would need to work with wireless card device-driver developers, he says.

Microsoft developers didn't actually commit to following Ellch's recommendations, but they did say it would be easy to implement in Vista. The company has already been searching for device-driver bugs, he says.

"Microsoft is really interested in trying to solve this problem," Ellch says. "That's what really impressed me the most. Microsoft is actively looking for bugs in device drivers, even though they didn't write them. That takes a lot of work, because Microsoft doesn't have the source code" for that.

So why not pitch this to the device-driver vendors themselves? "You won't find one that doesn't say 'we don't have bugs,' but they all do," Ellch says. "Anyone who has not had their device driver patched yet is going to."

— Kelly Jackson Higgins, Senior Editor, Dark Reading

  • Microsoft Corp. (Nasdaq: MSFT)
  • BreakingPoint Systems Kelly Jackson Higgins is the Executive Editor of Dark Reading. She is an award-winning veteran technology and business journalist with more than two decades of experience in reporting and editing for various publications, including Network Computing, Secure Enterprise ... View Full Bio

    Comment  | 
    Print  | 
    More Insights
  • Comments
    Threaded  |  Newest First  |  Oldest First
    Register for Dark Reading Newsletters
    White Papers
    Video
    Cartoon Contest
    Current Issue
    6 Emerging Cyber Threats That Enterprises Face in 2020
    This Tech Digest gives an in-depth look at six emerging cyber threats that enterprises could face in 2020. Download your copy today!
    Flash Poll
    State of Cybersecurity Incident Response
    State of Cybersecurity Incident Response
    Data breaches and regulations have forced organizations to pay closer attention to the security incident response function. However, security leaders may be overestimating their ability to detect and respond to security incidents. Read this report to find out more.
    Twitter Feed
    Dark Reading - Bug Report
    Bug Report
    Enterprise Vulnerabilities
    From DHS/US-CERT's National Vulnerability Database
    CVE-2020-10696
    PUBLISHED: 2020-03-31
    A path traversal flaw was found in Buildah in versions before 1.14.5. This flaw allows an attacker to trick a user into building a malicious container image hosted on an HTTP(s) server and then write files to the user's system anywhere that the user has permissions.
    CVE-2020-5344
    PUBLISHED: 2020-03-31
    Dell EMC iDRAC7, iDRAC8 and iDRAC9 versions prior to 2.65.65.65, 2.70.70.70, 4.00.00.00 contain a stack-based buffer overflow vulnerability. An unauthenticated remote attacker may exploit this vulnerability to crash the affected process or execute arbitrary code on the system by sending specially cr...
    CVE-2020-5292
    PUBLISHED: 2020-03-31
    Leantime before versions 2.0.15 and 2.1-beta3 has a SQL Injection vulnerability. The impact is high. Malicious users/attackers can execute arbitrary SQL queries negatively affecting the confidentiality, integrity, and availability of the site. Attackers can exfiltrate data like the users' and admini...
    CVE-2020-7009
    PUBLISHED: 2020-03-31
    Elasticsearch versions from 6.7.0 to 6.8.7 and 7.0.0 to 7.6.1 contain a privilege escalation flaw if an attacker is able to create API keys. An attacker who is able to generate an API key can perform a series of steps that result in an API key being generated with elevated privileges.
    CVE-2019-13495
    PUBLISHED: 2020-03-31
    In firmware version 4.50 of Zyxel XGS2210-52HP, multiple stored cross-site scripting (XSS) issues allows remote authenticated users to inject arbitrary web script via an rpSys.html Name or Location field.