Comment 0 for bug 1793029

Revision history for this message
Alex (akrohn) wrote :

On an openstack-ansible / newton setup with linuxbridge, a customer ran:

neutron port-update $port-uuid --allowed-address-pairs type=dict list=true ip_address=0.0.0.0/0

to bypass the ip source restriction (pfsense router and had to route packets).

The impact of running the above, was an allow all rule was added to all ports in the network, bypassing all security groups.

The iptables rule:

 905K 55M RETURN all -- * * 0.0.0.0/0 0.0.0.0/0 match-set NIPv44046d62c-59c8-4fd0-a547- src

used on all ports, now triggers as:

0.0.0.0/1
128.0.0.0/1

was added to the ipset NIPv44046d62c-59c8-4fd0-a547 (verified by looking at the ipset on the nova hosts). Removing the two lines from the ipset restored all security groups.

Expected result was to remove ip filtering on the single port.

This sounds similar to:

https://bugs.launchpad.net/neutron/+bug/1461054

but is marked fixed long ago.

I've marked this as a security bug as a change to a single port can bypass other ports security groups.