In Canonical LXD before 6.8, the backup import path validates project restrictions against backup/index.yaml in the supplied tar archive but creates the instance from backup/container/backup.yaml, a separate file in the same archive that is never checked against project restrictions. An authenticated remote attacker with instance-creation permission in a restricted project can craft a backup archive where backup.yaml carries restricted settings such as security.privileged=true or raw.lxc directives, bypassing all project restriction enforcement and allowing full host compromise.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:HCanonical Lxd
APPCanonical4.12 – 5.0.65.21.0 – 5.21.46.0 – 6.7
Related vulnerabilities
Canonical LXD — privilege escalation przez niekompletną listę blokad VM
Canonical LXD: privilege escalation do admina klastra przez brak walidacji pola Type
A privilege escalation vulnerability exists in LXD from 6.0 before 6.9, 5.21.0 before 5.21.5, and 5.0.0 before...
Broken Access Control in the devLXDInstancePatchHandler component of Canonical LXD allows an untrusted guest t...
Privilege Escalation in operations API in Canonical LXD <6.5 on multiple platforms allows attacker with read p...