Incus
Incus has an arbitrary file write on host via `exec-output` symlink in crafted image
Incus is a system container and virtual machine manager. Prior to version 7.2.0, the `record-output` parameter of the `/instances/$name/exec` endpoint stores the output of the command in the `exec-output` directory of the instance. If `exec-output` is a symlink, file named `exec_UUID.stdout` and `exec_UUID.stderr` can be written to an arbitrary location where the `.stdout` file will contain arbitrary content. This behavior can be abused for arbitrary command execution. Version 7.2.0 contains a patch.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- < 7.2.0
Fixed in 7.2.0
- >= 4.0.0, < 4.0.11
- >= 5.0.0, < 5.0.7
- >= 5.1.0, < 5.21.5
- >= 6.0.0, < 6.9.0
Fixed in 4.0.11, 5.0.7, 5.21.5, 6.9.0
Mitigation
Upgrade incus to 7.2.0 or later.
Upgrade lxd to 4.0.11 or 5.0.7 or 5.21.5 or 6.9.0 or later.
References
- Vendor advisory github.com/lxc/incus/security/advisories/GHSA-…
- Vendor advisory github.com/canonical/lxd/security/advisories/G…
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.