Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

reverse_https_proxy does not work #19694

Closed
smcintyre-r7 opened this issue Dec 5, 2024 · 0 comments · Fixed by #19740
Closed

reverse_https_proxy does not work #19694

smcintyre-r7 opened this issue Dec 5, 2024 · 0 comments · Fixed by #19740
Assignees
Labels

Comments

@smcintyre-r7
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants