Okay, so while deployments with libvirt < 1.3.4 shouldn't be affected, that's still effectively ~nobody where our supported releases+supported platforms are concerned? Also I like Nick's suggestion of noting removing user-allowed live migration if upgrades can't be applied immediately. In preparation for notifying our downstream stakeholders and eventual advisory publication, I propose we amend the impact description from comment #20 to read as follows...
Title: Live migration fails to update persistent domain XML
Reporter: Tadayoshi Hosoya (NEC) and Lee Yarwood (Red Hat)
Products: Nova
Affects: <19.3.1, >=20.0.0 <20.3.1, ==21.0.0
Description:
Tadayoshi Hosoya (NEC) and Lee Yarwood (Red Hat) reported a vulnerability in Nova live migration. By performing a soft reboot of an instance which 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. This can include block devices that map to different Cinder volumes on the destination to the source. The risk is increased significantly in non-default configurations allowing untrusted users to initiate live migrations, so administrators may consider temporarily disabling this in policy if they cannot upgrade immediately.
Okay, so while deployments with libvirt < 1.3.4 shouldn't be affected, that's still effectively ~nobody where our supported releases+supported platforms are concerned? Also I like Nick's suggestion of noting removing user-allowed live migration if upgrades can't be applied immediately. In preparation for notifying our downstream stakeholders and eventual advisory publication, I propose we amend the impact description from comment #20 to read as follows...
Title: Live migration fails to update persistent domain XML
Reporter: Tadayoshi Hosoya (NEC) and Lee Yarwood (Red Hat)
Products: Nova
Affects: <19.3.1, >=20.0.0 <20.3.1, ==21.0.0
Description:
Tadayoshi Hosoya (NEC) and Lee Yarwood (Red Hat) reported a vulnerability in Nova live migration. By performing a soft reboot of an instance which 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. This can include block devices that map to different Cinder volumes on the destination to the source. The risk is increased significantly in non-default configurations allowing untrusted users to initiate live migrations, so administrators may consider temporarily disabling this in policy if they cannot upgrade immediately.