Incus has an arbitrary file write on its client due to trusted image hash
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, an arbitrary file write exists in the Incus client when a malicious image server returns a crafted `Incus-Image-Hash` header. This can lead to arbitrary command execution as root on the server. Version 7.2.0 patches the issue.
From the CVE record · GitHub_M
Before version 7.2.0, the Incus client is vulnerable to arbitrary file writes when a malicious image server returns a crafted Incus-Image-Hash header. This can lead to arbitrary command execution as root on the server; the reported attack requires a response from a malicious image server.
Operators of Incus before 7.2.0, users of the listed Go packages, and Canonical LXD operators should check their exposure; affected LXD versions were not specified.