I didn't mean that console would be a requirement for the exploit, and indeed I overlooked the two-NICs scenario. Thanks for your feedback...I feared I was missing something ;)
That said, I have been thinking if ensuring a tag on the port after resize/migration operation suffices to mitigate the exploitation.
Ihar identified snippet of code [1] as potential contentious, and I wonder if along location [2] would be the only two areas required to be hardened.
I didn't mean that console would be a requirement for the exploit, and indeed I overlooked the two-NICs scenario. Thanks for your feedback...I feared I was missing something ;)
That said, I have been thinking if ensuring a tag on the port after resize/migration operation suffices to mitigate the exploitation.
Ihar identified snippet of code [1] as potential contentious, and I wonder if along location [2] would be the only two areas required to be hardened.
Thoughts?
Thanks,
Armando
[1] https:/ /github. com/openstack/ neutron/ blob/master/ neutron/ plugins/ ml2/drivers/ openvswitch/ agent/ovs_ neutron_ agent.py# L1426-L1436 /github. com/openstack/ neutron/ blob/newton- eol/neutron/ plugins/ ml2/drivers/ openvswitch/ agent/ovs_ neutron_ agent.py# L995
[2] https:/