rapid7 / metasploit-framework

Metasploit Framework
https://www.metasploit.com/
Other
33.86k stars 13.92k forks source link

Reverse Port Forward Can't Listen ipv4 #19218

Closed wgf4242 closed 2 months ago

wgf4242 commented 4 months ago

Steps to reproduce

  1. Get a Meterpreter shell (I used msfvenom -p linux/x64/meterpreter/reverse_tcp LHOST=127.0.0.1 LPORT=1234 -f elf > shell.elf )
  2. Add a reverse port forward portfwd add -l 5700 -L 127.0.0.1 -p 23 -R
  3. Observe the inaccurate message saying the reverse listener is open on Reverse TCP relay created: (remote) [::]:23 -> (local) 127.0.0.1:5700

[::]:23 is an ipv6 listener. What I need is an ipv4 listener.

Were you following a specific guide/tutorial or reading documentation?

If yes link the guide/tutorial or documentation you were following here, otherwise you may omit this section.

Expected behavior

Meterpreter should listen on 127.0.0.1:23

Current behavior

Listened on [::]:23.

[*] Reverse TCP relay created: (remote) [::]:23 -> (local) 127.0.0.1:5700
meterpreter > portfwd 

Active Port Forwards
====================

   Index  Local           Remote   Direction
   -----  -----           ------   ---------
   1      127.0.0.1:5700  [::]:23  Reverse

Metasploit version

└─$ msfconsole --version                                                                       
Framework Version: 6.3.27-dev
github-actions[bot] commented 3 months ago

Hi!

This issue has been left open with no activity for a while now.

We get a lot of issues, so we currently close issues after 60 days of inactivity. It’s been at least 30 days since the last update here. If we missed this issue or if you want to keep it open, please reply here. You can also add the label "not stale" to keep this issue open!

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.

github-actions[bot] commented 2 months ago

Hi again!

It’s been 60 days since anything happened on this issue, so we are going to close it. Please keep in mind that I’m only a robot, so if I’ve closed this issue in error please feel free to reopen this issue or create a new one if you need anything else.

As a friendly reminder: the best way to see this issue, or any other, fixed is to open a Pull Request.