
Metarget is a framework providing automatic constructions of vulnerable infrastructures.
Metarget = meta- + target, a framework providing automatic constructions of vulnerable infrastructures, used to deploy simple or complicated vulnerable cloud native targets swiftly and automatically.
During security researches, we might find that the deployment of vulnerable environment often takes much time, while the time spent on testing PoC or ExP is comparatively short. In the field of cloud native security, thanks to the complexity of cloud native systems, this issue is more terrible.
There are already some excellent security projects like Vulhub, VulApps in the open-source community, which pack vulnerable scenes into container images, so that researchers could utilize them and deploy scenes quickly.
However, these projects mainly focus on vulnerabilities in applications. What if we need to study the vulnerabilities in the infrastructures like Docker, Kubernetes and even Linux kernel?
Hence, we develop Metarget and hope to solve the deployment issue above to some extent. Furthermore, we also expect that Metarget could help to construct multilayer vulnerable cloud native scenes automatically.
In this project, we come up with concepts like installing vulnerabilities and installing vulnerable scenes. Why not install vulnerabilities just like installing softwares? We can do that, because our goals are security research and offensive security.
To be exact, we expect that:
metarget cnv install cve-2019-5736 will install Docker with CVE-2019-5736 onto the server.metarget cnv install cve-2018-1002105 will install Kubernetes with CVE-2018-1002105 onto the server.metarget cnv install kata-escape-2020 will install Kata-containers with CVE-2020-2023/2025/2026 onto the server.metarget cnv install cve-2016-5195 will install a kernel with DirtyCoW into the server.It's cool, right? No more steps. No RTFM. Execute one command and enjoy your coffee.
Furthermore, we expect that:
metarget appv install dvwa will install a DVWA target onto our vulnerable infrastructure.metarget appv install thinkphp-5-0-23-rce --external will install a ThinkPHP RCE vulnerability with NodePort service onto our vulnerable infrastructure.You can just run 5 commands below after installing a new Ubuntu and obtain a multi-layer vulnerable scene:
./metarget cnv install cve-2016-5195 # container escape with dirtyCoW
./metarget cnv install cve-2019-5736 # container escape with docker
./metarget cnv install cve-2018-1002105 # kubernetes single-node cluster with cve-2018-1002105
./metarget cnv install privileged-container # deploy a privileged container
./metarget appv install dvwa --external # deploy dvwa target
RCE, container escape, lateral movement, persistence, they are yours now.
More awesome functions are coming! Stay tuned :)
Note:
This project aims to provide vulnerable scenes for security research. The security of scenes generated is not guaranteed. It is NOT recommended to deploy components or scenes with Metarget on the Internet.
Clone the repository and install requirements:
git clone https://github.com/Metarget/metarget.git
cd metarget/
pip3 install -r requirements.txt
Begin to use Metarget and construct vulnerable scenes. For example:
./metarget cnv install cve-2019-5736
Currently unsupported.
Metarget needs to be run as root.
It is recommended to add --verbose option when debugging.
usage: metarget [-h] [-v] subcommand ...
automatic constructions of vulnerable infrastructures
positional arguments:
subcommand description
gadget cloud native gadgets (docker/k8s/...) management
cnv cloud native vulnerabilities management
appv application vulnerabilities management
optional arguments:
-h, --help show this help message and exit
-v, --version show program's version number and exit
Run ./metarget gadget list to see cloud native components supported currently.
usage: metarget gadget [-h] subcommand ...
positional arguments:
subcommand description
list list supported gadgets
install install gadgets
remove uninstall gadgets
optional arguments:
-h, --help show this help message and exit
Run
./metarget gadget list docker/k8s/containerd/runc/kernelto see cloud native components' supported versions currently.
Run:
./metarget gadget install docker --version 18.03.1
If the command above completes successfully, 18.03.1 Docker will be installed.
Run:
./metarget gadget install k8s --version 1.28.4
If the command above completes successfully, a 1.28.4 Kubernetes single-node cluster will be installed.
Supported Kubernetes version range: 1.9 – 1.33.
Note:
Metarget provides the following options for Kubernetes installation:
-v VERSION, --version VERSION
gadget version
--runtime {auto,docker,containerd}
container runtime for k8s (auto: containerd for k8s>=1.24, docker otherwise)
--runtime-version RUNTIME_VERSION
version of the container runtime to install alongside k8s.
For --runtime containerd: containerd.io apt version (e.g. 1.6.28).
For --runtime docker with k8s>=1.24: cri-dockerd version (e.g. 0.3.15).
Omit to install the latest/default version.
--cni-plugin CNI_PLUGIN
cni plugin, flannel by default
--pod-network-cidr POD_NETWORK_CIDR
pod network cidr, default cidr for each plugin by default
--taint-master taint master node or not
--domestic use domestic (Aliyun) mirrors for k8s images
Container runtime selection:
metarget gadget install docker). Use --runtime containerd to force containerd.--runtime auto default). No manual Docker installation needed.--runtime docker: Automatically installs cri-dockerd as the CRI shim (Docker must be pre-installed). Use --runtime-version to pin a specific cri-dockerd version.Examples:
# Install k8s 1.28 with containerd (auto-selected)
./metarget gadget install k8s --version 1.28.4
# Install k8s 1.28 with a specific containerd version
./metarget gadget install k8s --version 1.28.4 --runtime containerd --runtime-version 1.6.28
# Install k8s 1.28 with Docker + cri-dockerd (Docker must be pre-installed)
./metarget gadget install k8s --version 1.28.4 --runtime docker