Require msf/core/handler/bind_tcp

[space-r7]

Fixes #12267

This changes the msf/core/handler require in modules/payloads/singles/linux/x64/pingback_bind_tcp.rb to bind_tcp instead of reverse_tcp.

[bwatters-r7]

[bwatters-r7]

jenkins test this please

[bwatters-r7]

Woops. Not Jenkins, but Travis. Fixed anyway.

[bwatters-r7]

I mean, this change is 100% correct, but I cannot reproduce the original error. Regardless:

msf5 exploit(multi/handler) > show options

Module options (exploit/multi/handler):

   Name  Current Setting  Required  Description
   ----  ---------------  --------  -----------


Payload options (linux/x64/pingback_bind_tcp):

   Name   Current Setting  Required  Description
   ----   ---------------  --------  -----------
   LPORT  4567             yes       The listen port
   RHOST  192.168.134.163  no        The target address


Exploit target:

   Id  Name
   --  ----
   0   Wildcard Target


msf5 exploit(multi/handler) > run

[!] Unable to save UUID c88255fcd1374b40a2b990ecda1d165d to database -- database support not active
[*] Started bind TCP handler against 192.168.134.163:4567
[*] Pingback session 2 opened (192.168.135.168:37390 -> 192.168.134.163:4567) at 2019-09-03 14:11:22 -0500
[*] Incoming UUID = 6444732bbc414e948c888bf66167d0fe
[!] WARNING: UUID verification and logging is not available, because the database is not active.


[*] 192.168.134.163 - Pingback session 2 closed.  Reason: User exit
msf5 exploit(multi/handler) > 

FWIW, that the UUIDs do not match is not a problem. multi/hander creates a payload when it invokes the handler, then trashes it, because, well, the payload is already where it needs to be with multi/handler rather than a traditional create payload, throw and listen/callout.

[bwatters-r7]

Release Notes

This fixes a bug in the original release of linux/x64/pingback_bind_tcp where we brought in the wrong type of handler.