OpenStack Neutron's unsupported dport option prevents applying security groups
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.)
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2019-9735US | medium6.5 | — | ||
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… | ||||
references
External citations — patches, advisories, analysis.
- http://www.openwall.com/lists/oss-security/2019/03/18/2WEB
- http://www.securityfocus.com/bid/107390WEB
- https://access.redhat.com/errata/RHSA-2019:0879WEB
- https://access.redhat.com/errata/RHSA-2019:0916WEB
- https://access.redhat.com/errata/RHSA-2019:0935WEB
- https://github.com/openstack/neutronPACKAGE
- https://github.com/pypa/advisory-database/tree/main/vulns/neutron/PYSEC-2019-190.yamlWEB
- https://launchpad.net/bugs/1818385WEB
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan