Incus: Unbounded YAML Metadata Decode via Parsing
lxc incus
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lxc/incus/v6/cmd/incusd Go |
| No fix yet |
| github.com/lxc/incus Go |
| No fix yet |
| github.com/lxc/incus/v6 Go |
| No fix yet |
lxc incus
| Product | Affected | Fixed in |
|---|---|---|
| github.com/lxc/incus/v6/cmd/incusd Go |
| No fix yet |
| github.com/lxc/incus Go |
| No fix yet |
| github.com/lxc/incus/v6 Go |
| No fix yet |
Incus is a system container and virtual machine manager. Prior to version 7.0.0, user provided image and backup tarballs would be unpacked and YAML files parsed without any size restrictions. This was making it easy for an authenticated user to provide a crafted image or backup tarball that when parsed by Incus would lead to a very large YAML document being loaded into memory, potentially causing the entire server to run out of memory. This issue has been patched in version 7.0.0.
From the CVE record · GitHub_M
Before Incus 7.0.0, image and backup tarballs could be unpacked and their YAML files parsed without size limits. An authenticated user could supply a crafted tarball that causes Incus to load a very large YAML document, potentially exhausting server memory.
Operators running Incus before 7.0.0, including users of the listed Go packages, should check their deployments.