Canonical LXD
Arbitrary file write on LXD host via symlink in migration stream
Improper link resolution in the migration receive path in Canonical LXD versions 4.0 and later (fixed in 4.0.14, 5.0.10, 5.21.8 and 6.10) on Linux allows an authenticated client that can create instances or custom storage volumes in a project, or a malicious migration source server, to write attacker-controlled files to arbitrary paths on the target host as root, leading to full host compromise. The attacker does this with a crafted rsync or btrfs send stream that plants a symlink in the transferred volume, such as rootfs or root.img, and then writes through it.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.0.0, < 4.0.14
- >= 5.0.0, < 5.0.10
- >= 5.21.0, < 5.21.8
- >= 6.0, < 6.10
Fixed in 4.0.14, 5.0.10, 5.21.8, 6.10
Mitigation
Upgrade to LXD versions 4.0.14, 5.0.10, 5.21.8, 6.10 or later.
References
- 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.