Live-migrated instances are briefly able to inspect traffic for other instances on the same hypervisor.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 11.0.5, 12.0.3, 13.0.0.0b2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Live-migrated instances are briefly able to inspect traffic for other instances on the same hypervisor. This brief window could be extended indefinitely if the instance's port is set administratively down prior to live-migration and kept down after the migration is complete. This is possible due to the Open vSwitch integration bridge being connected to the instance during migration. When connected to the integration bridge, all traffic for instances using the same Open vSwitch instance would potentially be visible to the migrated guest, as the required Open vSwitch VLAN filters are only applied post-migration. Versions of openstack-neutron before 13.0.0.0b2, 12.0.3, 11.0.5 are vulnerable.
Timeline
- CVE published
- Record last updated
Affected versions
- The Openstack Project openstack-neutron
13.0.0.0b2, 12.0.3, 11.0.5
- neutronPyPI
From 7.0.0 · fixed in 11.0.5; From 12.0.0 · fixed in 12.0.3
- neutronPyPI
From 13.0.0.0b1 · fixed in 13.0.0.0b2
- neutronPyPI
From 12.0.0 · fixed in 12.0.3
- neutronPyPI
From 11.0.0 · fixed in 11.0.5