| 2018-09-17 22:41:14 |
Alex |
bug |
|
|
added bug |
| 2018-09-18 00:12:42 |
Jeremy Stanley |
description |
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. |
This issue is being treated as a potential security risk under embargo. Please do not make any public mention of embargoed (private) security vulnerabilities before their coordinated publication by the OpenStack Vulnerability Management Team in the form of an official OpenStack Security Advisory. This includes discussion of the bug or associated fixes in public forums such as mailing lists, code review systems and bug trackers. Please also avoid private disclosure to other individuals not already approved for access to this information, and provide this same reminder to those who are made aware of the issue prior to publication. All discussion should remain confined to this private bug report, and any proposed fixes should be added to the bug as attachments.
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. |
|
| 2018-09-18 00:12:53 |
Jeremy Stanley |
bug task added |
|
ossa |
|
| 2018-09-18 00:13:03 |
Jeremy Stanley |
ossa: status |
New |
Incomplete |
|
| 2018-09-18 00:13:23 |
Jeremy Stanley |
bug |
|
|
added subscriber Neutron Core Security reviewers |
| 2018-09-18 15:34:31 |
Brian Haley |
bug |
|
|
added subscriber Brian Haley |
| 2018-09-20 13:14:48 |
Jeremy Stanley |
information type |
Private Security |
Public |
|
| 2018-09-20 13:14:56 |
Jeremy Stanley |
ossa: status |
Incomplete |
Won't Fix |
|
| 2018-09-20 13:15:11 |
Jeremy Stanley |
bug task added |
|
ossn |
|
| 2018-09-20 13:15:27 |
Jeremy Stanley |
description |
This issue is being treated as a potential security risk under embargo. Please do not make any public mention of embargoed (private) security vulnerabilities before their coordinated publication by the OpenStack Vulnerability Management Team in the form of an official OpenStack Security Advisory. This includes discussion of the bug or associated fixes in public forums such as mailing lists, code review systems and bug trackers. Please also avoid private disclosure to other individuals not already approved for access to this information, and provide this same reminder to those who are made aware of the issue prior to publication. All discussion should remain confined to this private bug report, and any proposed fixes should be added to the bug as attachments.
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. |
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. |
|
| 2018-09-20 13:15:41 |
Jeremy Stanley |
tags |
|
security |
|
| 2018-09-24 12:29:33 |
Boden R |
neutron: importance |
Undecided |
Low |
|
| 2018-09-24 12:29:33 |
Boden R |
neutron: status |
New |
Triaged |
|
| 2018-09-24 12:30:00 |
Boden R |
tags |
security |
api-ref security |
|
| 2019-05-27 13:30:27 |
OpenStack Infra |
neutron: status |
Triaged |
In Progress |
|
| 2019-05-27 13:30:27 |
OpenStack Infra |
neutron: assignee |
|
Slawek Kaplonski (slaweq) |
|
| 2019-05-29 15:46:22 |
OpenStack Infra |
neutron: assignee |
Slawek Kaplonski (slaweq) |
Brian Haley (brian-haley) |
|
| 2019-05-29 16:32:32 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
