Rapid7 Vulnerability & Exploit Database

Wireshark LWRES Dissector getaddrsbyname_request Buffer Overflow (loop)

Back to Search

Wireshark LWRES Dissector getaddrsbyname_request Buffer Overflow (loop)

Disclosed
01/27/2010
Created
05/30/2018

Description

The LWRES dissector in Wireshark version 0.9.15 through 1.0.10 and 1.2.0 through 1.2.5 allows remote attackers to execute arbitrary code due to a stack-based buffer overflow. This bug found and reported by babi. This particular exploit targets the dissect_getaddrsbyname_request function. Several other functions also contain potentially exploitable stack-based buffer overflows. The Windows version (of 1.2.5 at least) is compiled with /GS, which prevents exploitation via the return address on the stack. Sending a larger string allows exploitation using the SEH bypass method. However, this packet will usually get fragmented, which may cause additional complications. NOTE: The vulnerable code is reached only when the packet dissection is rendered. If the packet is fragmented, all fragments must be captured and reassembled to exploit this issue. This version loops, sending the packet every X seconds until the job is killed.

Author(s)

  • babi
  • jduck <jduck@metasploit.com>
  • redsand

Platform

Linux,OSX,Windows

Development

Module Options

To display the available options, load the module within the Metasploit console and run the commands 'show options' or 'show advanced':

msf > use exploit/multi/misc/wireshark_lwres_getaddrbyname_loop
msf exploit(wireshark_lwres_getaddrbyname_loop) > show targets
    ...targets...
msf exploit(wireshark_lwres_getaddrbyname_loop) > set TARGET < target-id >
msf exploit(wireshark_lwres_getaddrbyname_loop) > show options
    ...show and set options...
msf exploit(wireshark_lwres_getaddrbyname_loop) > exploit

Time is precious, so I don’t want to do something manually that I can automate. Leveraging the Metasploit Framework when automating any task keeps us from having to re-create the wheel as we can use the existing libraries and focus our efforts where it matters.

– Jim O’Gorman | President, Offensive Security

;