Skip to content

Conversation

@thiagomayllart
Copy link

Hello everyone!!

I just added fully working reverse port forward functionality to covenant. It doesn't bind to any port in the machine with the Grunt. The Grunt only connects to the destination and the C2.

The user can connect to the VPS and the selected port. The C2 is responsible to bind to a port and forward the traffic to the Grunt and then, to the destination. The whole procedure is pretty much similar to portfwd from meterpreter.

I tried to add the functionality directly to a task without touching other things... but that was not possible. I had to add a PortForward dummy task only to have the Task option in the Grunts. The handlers are actually in the new GruntHTTPPortForward and, in the CovenantService (responsible for bind to the port and forwarding the traffic).

I also modified the DbInitializer only to add the new Grunt.

In case you guys need more details feel free to ask.

Thank you!!

Added Grunt with functionality of port forwarding.
Added the Grunt with the Port Forward functionality.
This stager is exactly the same as the one from GruntHTTP.
@caseyvsilver1515
Copy link

this is so awesome, it is a feature i have been wanting to see added. I also would love a socks server added. Thanks for doing this.

@sempervictus
Copy link

Wow, amazingly the meterp/metasploit version of this is actually simpler in terms of code volume. Kudos. Being able to present services remotely is key - DHCP and DNS alone can be priceless, and stateful stuff inside the trusted intranet zone is always fun.

@dustinwloring1988
Copy link

Any update on this ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants