Incus vulnerable to local privilege escalation through custom storage volumes
lxc incus
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lxc/incus/v6 Go |
|
|
| github.com/lxc/incus Go |
| No fix yet |
lxc incus
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lxc/incus/v6 Go |
|
|
| github.com/lxc/incus Go |
| No fix yet |
Incus is a system container and virtual machine manager. An issue in versions prior to 6.0.6 and 6.19.0 affects any Incus user in an environment where an unprivileged user may have root access to a container with an attached custom storage volume that has the `security.shifted` property set to `true` as well as access to the host as an unprivileged user. The most common case for this would be systems using `incus-user` with the less privileged `incus` group to provide unprivileged users with an isolated restricted access to Incus. Such users may be able to create a custom storage volume with the necessary property (depending on kernel and filesystem support) and can then write a setuid binary from within the container which can be executed as an unprivileged user on the host to gain root privileges. A patch for this issue is expected in versions 6.0.6 and 6.19.0. As a workaround, permissions can be manually restricted until a patched version of Incus is deployed.
From the CVE record · GitHub_M
Incus versions prior to 6.0.6 and 6.19.0 are affected when an unprivileged user has root access inside a container with an attached custom storage volume configured with `security.shifted=true`, and also has unprivileged access to the host. That user may be able to write a setuid binary in the container and execute it on the host to gain root privileges.
Operators running affected Incus versions should check their installations, including Go package `github.com/lxc/incus/v6` versions 6.1.0 through before 6.19.0 and `github.com/lxc/incus`, for which no fixed version is listed.