[Openstack-security] [Bug 1793029] Re: adding 0.0.0.0/0 address pair to a port bypasses all other vm security groups
Author: Slawek Kaplonski <skaplons at redhat.com>
Date: Mon May 27 02:45:15 2019 +0200
[api-ref] Add short warning about ANY IP address in allowed address pair
** Changed in: neutron
Status: In Progress => Fix Released
You received this bug notification because you are a member of OpenStack
Security SIG, which is subscribed to OpenStack.
adding 0.0.0.0/0 address pair to a port bypasses all other vm
Status in neutron:
Status in OpenStack Security Advisory:
Status in OpenStack Security Notes:
On an openstack-ansible / newton setup with linuxbridge, a customer
neutron port-update $port-uuid --allowed-address-pairs type=dict
to bypass the ip source restriction (pfsense router and had to route
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:
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:
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.
To manage notifications about this bug go to: