Incus nil-pointer dereference in storage bucket import allows denial of service
lxc incus
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lxc/incus/v6/cmd/incusd Go |
|
|
| github.com/lxc/incus Go |
| No fix yet |
| github.com/lxc/incus/v6 Go |
|
lxc incus
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lxc/incus/v6/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. In versions before 7.0.0, missing validation logic in the storage bucket import logic allows an authenticated user with access to the storage bucket feature to cause the Incus daemon to crash. The vulnerability is present in the backup metadata handling logic, where the daemon processes the index.yaml file from an imported archive and accesses members of the parsed backup configuration without first verifying that the configuration object was initialized. A malicious or malformed index.yaml that omits the config block causes a nil-pointer dereference during bucket import operations and terminates the daemon. Repeated use of this issue can be used to keep Incus offline, causing a denial of service. This issue is fixed in version 7.0.0.
From the CVE record · GitHub_M
Incus before 7.0.0 does not validate backup metadata during storage bucket import. An authenticated user with access to the storage bucket feature can import an archive whose index.yaml omits the config block, crashing the daemon; repeated imports can keep it offline.
Check deployments using Incus before 7.0.0, including Go packages github.com/lxc/incus/v6/cmd/incusd and github.com/lxc/incus/v7 below 7.0.0; the listed github.com/lxc/incus and github.com/lxc/incus/v6 packages have no fixed version.