Описание
Incus has an arbitrary file read+write on host via rootfs/ symlink in malicious image
Summary
A specially crafted image can be used to read or create/write arbitrary files on the host; possibly leading to arbitrary command execution.
Details
Incus validates an image as soon as it sees a normal metadata.yaml and a rootfs/ entry, but full extraction can later process a duplicate top-level rootfs symlink. Later, the stopped-container file API opens d.RootfsPath() and passes that file descriptor to forkfile, which chroots to it.
In practice, this allows a malicious actor to access the host's filesystem with root privileges.
PoC
Below, we map the container's rootfs to / on the host, but it can be mapped anywhere. We then retrieve the host's /etc/shadow file and create a file in /.
Impact
Arbitrary file read and write on the host via unsanitized symlink; possibly leading to command execution.
Пакеты
github.com/lxc/incus/v7/cmd/incusd
< 7.2.0
7.2.0