Incus has a restricted project bypass leading to arbitrary command execution
lxc incus · canonical lxd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lxc/incus/v7/cmd/incusd Go |
|
|
| github.com/lxc/incus Go |
| No fix yet |
| github.com/lxc/incus/v6 Go |
|
lxc incus · canonical lxd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lxc/incus/v7/cmd/incusd Go |
|
|
| github.com/lxc/incus Go |
| No fix yet |
| github.com/lxc/incus/v6 Go |
|
| No fix yet |
| github.com/lxc/incus/v7 Go |
|
|
Incus is a system container and virtual machine manager. Prior to version 7.2.0, instance snapshots ignore the `restricted.containers.lowlevel=block` setting; allowing for arbitrary command execution on the Incus server by abusing lowlevel hooks such as `raw.lxc` and `raw.qemu`. Version 7.2.0 patches the issue.
From the CVE record · GitHub_M
Before Incus 7.2.0, instance snapshots ignore the `restricted.containers.lowlevel=block` setting. An attacker can abuse low-level hooks such as `raw.lxc` and `raw.qemu` to execute arbitrary commands on the Incus server. The input does not specify network access, authentication, or user-interaction requirements.
Operators of Incus before 7.2.0, users of the listed Incus Go packages, and Canonical LXD operators should check their deployments; no affected LXD versions are specified.