← 返回列表

Metarget:构建云原生基础设施靶场

聚合站 SecWiki技术 入库 2026-11-18T17:39:07

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:

It's cool, right? No more steps. No RTFM. Execute one command and enjoy your coffee.

Furthermore, we expect that:

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.

./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.

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:

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
# Install k8s 1.20 with containerd (forced on an older version)
./metarget gadget install k8s --version 1.20.15 --runtime containerd

Metarget supports deployment of multi-node cluster. If you want to add more nodes into the cluster, you can copy tools/install_k8s_worker.sh script and run it on each worker nodes after the successful installation of single-node cluster.

./metarget gadget install kata --version 1.10.0
If the command above completes successfully, 1.10.0 Kata-containers will be installed.

You can also specify the type of kata runtime (qemu/clh/fc/...) with --kata-runtime-type option, which is qemu by default.

./metarget gadget install kernel --version 5.7.5
If the command above completes successfully, 5.7.5 kernel will be installed.

Currently, Metarget installs kernels in 2 ways:

  1. apt
  2. if apt package is not available, download *.deb remotely from Ubuntu and try to install

After successful installation of kernel, reboot of system is needed. Metarget will prompt to reboot automatically.

./metarget gadget install containerd --version 1.7.14
If the command above completes successfully, 1.7.14 containerd will be installed and automatically configured as a Kubernetes CRI runtime (SystemdCgroup = true), ready to use with metarget gadget install k8s.

./metarget gadget install runc --version 1.1.6
If the command above completes successfully, 1.1.6 runc will be installed.

usage: metarget cnv [-h] subcommand ...
positional arguments:
  subcommand  description
    list      list supported cloud native vulnerabilities
    install   install cloud native vulnerabilities
    remove    uninstall cloud native vulnerabilities
optional arguments:
  -h, --help  show this help message and exit

Run ./metarget cnv list to see vulnerable scenes related to cloud native components supported currently.

If the command above completes successfully, Docker with CVE-2019-5736 will be installed。

./metarget cnv install cve-2018-1002105
If the command above completes successfully, Kubernetes with CVE-2018-1002105 will be installed。

./metarget cnv install kata-escape-2020
If the command above completes successfully, Kata-containers with CVE-2020-2023/2025/2026 will be installed。

./metarget cnv install cve-2016-5195
If the command above completes successfully, kernel with CVE-2016-5195 will be installed。

usage: metarget appv [-h] subcommand ...
positional arguments:
  subcommand  description
    list      list supported application vulnerabilities
    install   install application vulnerabilities
    remove    uninstall application vulnerabilities
optional arguments:
  -h, --help  show this help message and exit

Run ./metarget appv list to see vulnerable scenes related to cloud native applications supported currently.

Before deploying application vulnerable scenes, you should install Docker and Kubernetes firstly. You can use Metarget to install Docker and Kubernetes.

./metarget appv install dvwa
If the command above completes successfully, DVWA will be deployed as Deployment and Service resources in current Kubernetes.

Depending on the user's network environment, ubuntu version, and Docker version, one-click installation of the vulnerability environment through automated scripts still occasionally fails, so we provide the vulnerability environment image for the first time.

Run the following command to build the target vulnerability environment image:

sudo docker build -t vuln-docker-24.0.7 -f vuln-docker-24.0.7 .
Run the following command to run the target vulnerability environment image:

docker run vuln-XXX
Developing, currently not supported.

If there is an asterisk (*) following the name of one vulnerable scene, you need to read the note related to it below the whole table for further details.

Name Class Type CVSS 3.x Writeup ATT&CK map
cve-2018-15664 docker container_escape 7.5 privilege escalation/escape to host Persistence/escape to host Lateral movement/escape to host Defense Bypass/Build an image on the host
cve-2019-13139 docker command_execution 8.4 link
cve-2019-14271 docker container_escape 9.8 link
cve-2020-15257 docker/containerd container_escape 5.2 link
cve-2019-5736 docker/runc container_escape 8.6
cve-2019-16884 docker/runc container_escape 7.5
cve-2021-30465* docker/runc container_escape 7.6 link
cve-2024-21626 docker/runc container_escape 8.6
cve-2017-1002101 k8s container_escape 9.6 link
cve-2018-1002105 k8s privilege_escalation 9.8
cve-2018-1002100 k8s/kubectl container_escape 5.5
cve-2019-1002101 k8s/kubectl container_escape 5.5
cve-2019-11246 k8s/kubectl container_escape 6.5
cve-2019-11249 k8s/kubectl container_escape 6.5
cve-2019-11251 k8s/kubectl container_escape 5.7
cve-2019-11253 k8s denial_of_service 7.5
cve-2019-9512 k8s denial_of_service 7.5
cve-2019-9514 k8s denial_of_service 7.5
cve-2019-9946 k8s traffic_interception 7.5
cve-2020-8554 k8s man_in_the_middle 5.0
cve-2020-10749 k8s/kubernetes-cni man_in_the_middle 6.0
cve-2020-8555 k8s server_side_request_forgery 6.3
cve-2020-8557 k8s denial_of_service 5.5
cve-2020-8558 k8s exposure_of_service 8.8
cve-2020-8559 k8s privilege_escalation 6.8
cve-2021-25741 k8s container_escape 8.1
cve-2022-0811 k8s container_escape 8.8 link
cve-2016-5195 kernel container_escape 7.8
cve-2016-8655 kernel privilege_escalation 7.8
cve-2017-6074 kernel privilege_escalation 7.8
cve-2017-7308 kernel container_escape 7.8 link
cve-2017-16995 kernel privilege_escalation 7.8
cve-2017-1000112 kernel container_escape 7.0 link
cve-2018-18955 kernel privilege_escalation 7.0
cve-2020-14386 kernel container_escape 7.8
cve-2021-3493 kernel privilege_escalation 7.8 link
cve-2021-4204 kernel privilege_escalation -
cve-2021-22555 kernel container_escape 7.8
cve-2022-0185 kernel container_escape 8.4
cve-2022-0492 kernel container_escape 7.8 link
cve-2022-0847 kernel container_escape 7.8 link
cve-2022-0995* kernel privilege_escalation 7.1 link
cve-2022-25636* kernel privilege_escalation 7.8
cve-2022-23222 kernel privilege_escalation 7.8
cve-2022-27666* kernel privilege_escalation 7.8
cve-2023-3269* kernel privilege_escalation 7.8
kata-escape-2020 kata-containers container_escape 6.3/8.8/8.8
cve-2020-27151 kata-containers container_escape 8.8
cap_dac_read_search-container config container_escape - link
cap_sys_admin-container config container_escape -
cap_sys_ptrace-container config container_escape -
cap_sys_module-container config container_escape - link
privileged-container config container_escape - link
k8s_backdoor_daemonset config persistence - link
k8s_backdoor_cronjob config persistence - link
k8s_shadow_apiserver config persistence - link
k8s_node_proxy config privilege_escalation - link
mount-docker-sock mount container_escape - link
mount-host-etc mount container_escape -
mount-host-procfs mount container_escape - link
mount-var-log mount container_escape - link

These scenes are mainly derived from other open-source projects:

We express sincere gratitude to projects above!

Metarget converts scenes in projects above to Deployments and Services resources in Kubernetes (thanks to kompose).

To list vulnerable scenes related to cloud native applications supported by Metarget, just run:

./metarget appv list
- For the deployment of Confluence's vulnerability CVE-2019-3396, you may refer to Vulhub, while the address of PostgreSQL should be cve-2019-3396-db, not db in Vulhub.

One of Metarget's goals is to facilitate more rapid construction of vulnerable environments when vulnerabilities occur. Also, it could be used to construct all the integrated vulnerable scenes whenever you want.

To keep Metarget up-to-date, the vulnerable scenes lists (both cnv and appv) will be maintained.

YAML is used in Metarget to describe & integrate vulnerable scenes. Currently, scenes in two layers, cnv (in vulns_cn/) and appv (in vulns_app/), are supported.

Maintenance from the community is appreciated and welcome. Hope that we can gather and share our knowledge and researches in the context of Metarget, and promote the development of cloud native security.

Currently, you can contribute to Metarget in two ways:

  1. Submit YAML files of new cloud native vulnerabilities (cnv).
  2. Submit YAML files of new cloud native application vulnerabilities (appv).

Please see CONTRIBUTING.md for details.

We eagerly welcome collaboration with universities, research institutions, and other academic entities! Metarget is dedicated to being an ideal experimental platform for cutting-edge research in the field of cloud-native security. We believe that cloud-native security will be a forefront topic in the future of network security, and Metarget provides an ideal research environment for this.

Through our robust and flexible framework, you can delve into the security challenges of cloud-native environments, discover and explore innovative solutions, and contribute your expertise and findings to the entire industry's development.

Metarget offers the following distinctive support to collaborators:

  1. Diverse experimental scenarios: Utilize Metarget to effortlessly build various vulnerable cloud-native target environments, covering a spectrum of experiment scenarios from simple to complex, such as cloud-native e-commerce platform and cloud-native online course system.
  2. cloud native vulnerable images: Without any scripting assistance, the vulnerability environment is readily available
  3. Support for multiple versions of Kernel, Kubernetes, and other cloud-native components: Metarget consistently updates to support the latest versions of components, ensuring that you can use the latest technologies in your experiments.
  4. Customization of Ubuntu versions: We will tailor Ubuntu versions based on your experimental requirements, providing you with a more flexible experimental environment configuration.
  5. Automatic generation of multi-node cloud-native clusters: Metarget offers the functionality to automatically create multi-node cloud-native target clusters, enhancing the realism and depth of your research.
  6. ...

Joining Metarget provides you with comprehensive technical support and abundant collaboration opportunities, allowing you to explore the forefront of cloud-native security and contribute your unique insights to the future development of network security. We look forward to your participation in collectively shaping a new chapter in cybersecurity research!

It is not a Kubernetes, but a vulnerable infrastructure with three gears which could not work well (vulnerable) :)

Metarget is licensed under Apache License 2.0. See LICENSE for the full license text.

原文链接:https://github.com/Metarget/metarget