OpenStack Nova Live migration fails to update persistent domain XML
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| nova PyPI |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| nova PyPI |
|
|
An issue was discovered in Guest.migrate in virt/libvirt/guest.py in OpenStack Nova before 19.3.1, 20.x before 20.3.1, and 21.0.0. By performing a soft reboot of an instance that has previously undergone live migration, a user may gain access to destination host devices that share the same paths as host devices previously referenced by the virtual machine on the source host. This can include block devices that map to different Cinder volumes at the destination than at the source. Only deployments allowing host-based connections (for instance, root and ephemeral devices) are affected.
From the CVE record · mitre
Guest.migrate in OpenStack Nova can expose destination host devices to a user who soft-reboots an instance after live migration. This affects only deployments allowing host-based connections; exposed devices can include block devices mapped to different Cinder volumes on the destination host.
Operators running OpenStack Nova or the PyPI nova package before 19.3.1, 20.x before 20.3.1, or 21.0.0 should check their deployments.