You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While testing #19609 it became apparent that the 32-bit windows stager reverse_https_proxy was not working. I went back and tested if it worked before the changes in the PR and it still didn't work which led me to bisect the issue leading me to identify 3cf375c as the breaking commit. In that commit, Metasploit will say that the Meterpreter session is established however the communication isn't properly working and you can't interact with the session. A few commits later and the payload starts to crash altogether.
Based on this stager having been broken for over 5 years, there being no tickets noting that it's not working and the functionality having been superseded by the reverse_https stager and its HttpProxy* datastore options, I think the stager should be removed.
The text was updated successfully, but these errors were encountered:
While testing #19609 it became apparent that the 32-bit windows stager
reverse_https_proxy
was not working. I went back and tested if it worked before the changes in the PR and it still didn't work which led me to bisect the issue leading me to identify 3cf375c as the breaking commit. In that commit, Metasploit will say that the Meterpreter session is established however the communication isn't properly working and you can't interact with the session. A few commits later and the payload starts to crash altogether.Based on this stager having been broken for over 5 years, there being no tickets noting that it's not working and the functionality having been superseded by the
reverse_https
stager and itsHttpProxy*
datastore options, I think the stager should be removed.The text was updated successfully, but these errors were encountered: