Incus has a project restriction bypass for custom volume copy across projects
lxc incus · canonical lxd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lxc/incus/v7 Go |
|
|
| github.com/lxc/incus/v6 Go |
| No fix yet |
| github.com/lxc/incus Go |
lxc incus · canonical lxd
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lxc/incus/v7 Go |
|
|
| github.com/lxc/incus/v6 Go |
| No fix yet |
| github.com/lxc/incus Go |
≤ 0.7.0all versions| No fix yet |
Incus is a system container and virtual machine manager. Prior to version 7.2.0, missing authorization checks exist for custom volume copying where an attacker knowing the name of a project that they don't have access to and the name of a custom volume in that project can copy the custom volume to a new project. This issue could allow an attacker to access secrets in custom volumes they are not authorized to access. Version 7.2.0 patches the issue.
From the CVE record · GitHub_M
Incus has missing authorization checks when copying custom volumes. An attacker who knows the name of a project they cannot access and a custom volume in it can copy that volume to a new project, potentially exposing secrets. The input does not specify whether the attack requires network or local access, authentication, or user interaction.
Check deployments of Incus and Canonical LXD, particularly Go packages github.com/lxc/incus/v7 before 7.2.0, github.com/lxc/incus/v6 through 6.23.0, and github.com/lxc/incus through 0.7.0; affected LXD versions are not specified.