OpenStack Neutron's unsupported dport option prevents applying security groups
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| neutron PyPI |
|
|
| Product | Affected | Fixed in |
|---|---|---|
| neutron PyPI |
|
|
An issue was discovered in the iptables firewall module in OpenStack Neutron before 10.0.8, 11.x before 11.0.7, 12.x before 12.0.6, and 13.x before 13.0.3. By setting a destination port in a security group rule along with a protocol that doesn't support that option (for example, VRRP), an authenticated user may block further application of security group rules for instances from any project/tenant on the compute hosts to which it's applied. (Only deployments using the iptables security group driver are affected.)
From the CVE record · mitre
In deployments using the iptables security group driver, an authenticated user can create a security group rule with a destination port and a protocol that does not support one. This may block further application of security group rules for instances from any project or tenant on affected compute hosts.
Operators running OpenStack Neutron versions before 10.0.8, 11.0.0–11.0.6, 12.0.0–12.0.5, or 13.0.0–13.0.2 with the iptables security group driver should check their deployments.