Incus vulnerable to arbitrary file read and write through pongo templates
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. Prior to version 6.23.0, instance template files can be used to cause arbitrary read or writes as root on the host server. Incus allows for pongo2 templates within instances which can be used at various times in the instance lifecycle to template files inside of the instance. This particular implementation of pongo2 within Incus allowed for file read/write but with the expectation that the pongo2 chroot feature would isolate all such access to the instance's filesystem. This was allowed such that a template could theoretically read a file and then generate a new version of said file. Unfortunately the chroot isolation mechanism is entirely skipped by pongo2 leading to easy access to the entire system's filesystem with root privileges. Version 6.23.0 patches the issue.
From the CVE record · GitHub_M
Incus instance templates before version 6.23.0 can read or write files outside the instance because pongo2 skips the expected filesystem isolation. An attacker who can supply an instance template can read or write files on the host as root; the input does not specify authentication requirements or user interaction.
Teams running Incus before 6.23.0, or using Go packages github.com/lxc/incus/v6 before 6.23.0 or github.com/lxc/incus through 0.7.0, should check their deployments.