nettitude / PoshC2

A proxy aware C2 framework used to aid red teamers with post-exploitation and lateral movement.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

[HELP] - Cannot make it work

b4b857f6ee opened this issue · comments

Description

My configuration isn't working, i can't get the payload remote access nothing work :/

Execution Environment:

All of this must be filled in
Ubuntu 18.04 update and VM
------ | ------
Full Posh version (all the text between the === at the top of the Implant Handler) | v6.0
OS & version | Ubuntu 18.04

Implant Info

  • What implant does the problem occur on? All
  • How was the implant created? Running a default payload

Defensive Technologies

  • Nothing

To Reproduce

Steps to reproduce the behavior:
Juste install by cloning the github
And try to make it work with Apache 2.

Expected behavior

Remote access with the payload

Screenshots

My local system is in 10.0.0.5
for the Posh, 10.0.0.11 for the Apache
and the client is 192.168.108.4

This is the Apache configuration
image

The redirection looks like to work because i have this :
image

And this is my posh-config

image

And the whitelist file
image

Attach files if required

Additional context

The communication is good between the both side but i can't get the payload to connect my VM, i don't understand why.
Thank you for your help :)

Hey, thanks for the detailed report!

Is there anything in the webserver.log for PoshC2 (in the project directory)?
Are you also able to upload or show the apache access.log & error.log files?

Ah no, I see the issue, the kill date is in the past so the implants won't beacon... try updating that with set-killdate <date> from the ImplantHandler (or just change it in the config and start a new project)

xD, i didn't see it ahah.
It's work now! Thank you !