Windows Inject Reflective PE Files, Windows x64 Bind TCP Stager - Metasploit
This page contains detailed information about how to use the payload/windows/x64/peinject/bind_tcp metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Windows Inject Reflective PE Files, Windows x64 Bind TCP Stager
Module: payload/windows/x64/peinject/bind_tcp
Source code: modules/payloads/stagers/windows/x64/bind_tcp.rb
Disclosure date: -
Last modification time: 2020-09-22 02:56:51 +0000
Supported architecture(s): x64
Supported platform(s): Windows
Target service / protocol: -
Target network port(s): -
List of CVEs: -
Inject a custom native PE file into the exploited process using a reflective PE loader. The reflective PE loader will execute the pre-mapped PE image starting from the address of entry after performing image base relocation and API address resolution. This module requires a PE file that contains relocation data and a valid (uncorrupted) import table. PE files with CLR(C#/.NET executables), bounded imports, and TLS callbacks are not currently supported. Also PE files which use resource loading might crash. . Listen for a connection (Windows x64)
Module Ranking and Traits
Module Ranking:
- normal: The exploit is otherwise reliable, but depends on a specific version and can't (or doesn't) reliably autodetect. More information about ranking can be found here.
Basic Usage
msf > use payload/windows/x64/peinject/bind_tcp
msf payload(bind_tcp) > show options
... show and set options ...
msf payload(bind_tcp) > generate
To learn how to generate payload/windows/x64/peinject/bind_tcp with msfvenom, please read this.
Required Options
- PE: The local path to the PE file to upload
Go back to menu.
Msfconsole Usage
Here is how the windows/x64/peinject/bind_tcp payload looks in the msfconsole:
msf6 > use payload/windows/x64/peinject/bind_tcp
msf6 payload(windows/x64/peinject/bind_tcp) > show info
Name: Windows Inject Reflective PE Files, Windows x64 Bind TCP Stager
Module: payload/windows/x64/peinject/bind_tcp
Platform: Windows
Arch: x64
Needs Admin: No
Total size: 483
Rank: Normal
Provided by:
ege <[email protected]>
sf <[email protected]>
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
EXITFUNC thread yes Exit technique (Accepted: '', seh, thread, process, none)
LPORT 4444 yes The listen port
PE yes The local path to the PE file to upload
RHOST no The target address
Description:
Inject a custom native PE file into the exploited process using a
reflective PE loader. The reflective PE loader will execute the
pre-mapped PE image starting from the address of entry after
performing image base relocation and API address resolution. This
module requires a PE file that contains relocation data and a valid
(uncorrupted) import table. PE files with CLR(C#/.NET executables),
bounded imports, and TLS callbacks are not currently supported. Also
PE files which use resource loading might crash. . Listen for a
connection (Windows x64)
Module Options
This is a complete list of options available in the windows/x64/peinject/bind_tcp payload:
msf6 payload(windows/x64/peinject/bind_tcp) > show options
Module options (payload/windows/x64/peinject/bind_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
EXITFUNC thread yes Exit technique (Accepted: '', seh, thread, process, none)
LPORT 4444 yes The listen port
PE yes The local path to the PE file to upload
RHOST no The target address
Advanced Options
Here is a complete list of advanced options supported by the windows/x64/peinject/bind_tcp payload:
msf6 payload(windows/x64/peinject/bind_tcp) > show advanced
Module advanced options (payload/windows/x64/peinject/bind_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
EnableStageEncoding false no Encode the second stage payload
PayloadUUIDName no A human-friendly name to reference this unique payload (requires tracking)
PayloadUUIDRaw no A hex string representing the raw 8-byte PUID value for the UUID
PayloadUUIDSeed no A string to use when generating the payload UUID (deterministic)
PayloadUUIDTracking false yes Whether or not to automatically register generated UUIDs
PingbackRetries 0 yes How many additional successful pingbacks
PingbackSleep 30 yes Time (in seconds) to sleep between pingbacks
PrependMigrate false yes Spawns and runs shellcode in new process
PrependMigrateProc no Process to spawn and run shellcode in
StageEncoder no Encoder to use if EnableStageEncoding is set
StageEncoderSaveRegisters no Additional registers to preserve in the staged payload if EnableStageEncoding is set
StageEncodingFallback true no Fallback to no encoding if the selected StageEncoder is not compatible
VERBOSE false no Enable detailed status messages
WORKSPACE no Specify the workspace for this module
Go back to menu.
Related Pull Requests
- #14202 Merged Pull Request: Implement the zeitwerk autoloader within lib/msf/core
- #13980 Merged Pull Request: Reflective PE Payloads Added
Go back to menu.
See Also
Check also the following modules related to this module:
- payload/windows/x64/peinject/bind_ipv6_tcp
- payload/windows/x64/peinject/bind_ipv6_tcp_uuid
- payload/windows/x64/peinject/bind_named_pipe
- payload/windows/x64/peinject/bind_tcp_rc4
- payload/windows/x64/peinject/bind_tcp_uuid
- payload/windows/x64/peinject/reverse_named_pipe
- payload/windows/x64/peinject/reverse_tcp
- payload/windows/x64/peinject/reverse_tcp_rc4
- payload/windows/x64/peinject/reverse_tcp_uuid
Authors
- ege <egebalci[at]pm.me>
- sf
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.