A race-condition flaw was discovered in openstack-neutron before 7.2.0-12.1, 8.x before 8.3.0-11.1, 9.x before 9.3.1-2.1, and 10.x before 10
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.2.0-12.1, 8.3.0-11.1, 9.3.1-2.1, 10.0.2-1.1
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
A race-condition flaw was discovered in openstack-neutron before 7.2.0-12.1, 8.x before 8.3.0-11.1, 9.x before 9.3.1-2.1, and 10.x before 10.0.2-1.1, where, following a minor overcloud update, neutron security groups were disabled. Specifically, the following were reset to 0: net.bridge.bridge-nf-call-ip6tables and net.bridge.bridge-nf-call-iptables. The race was only triggered by an update, at which point an attacker could access exposed tenant VMs and network resources.
Timeline
- CVE published
- Record last updated
Affected versions
- Red Hat openstack-neutron
openstack-neutron-10.0.2-1.1, openstack-neutron-8.3.0-11.1, openstack-neutron-9.3.1-2.1, openstack-neutron-7.2.0-12.1
- neutronPyPI
fixed in 7.2.0-12.1
- neutronPyPI
From 8.0.0 · fixed in 8.3.0-11.1
- neutronPyPI
From 9.0.0 · fixed in 9.3.1-2.1
- neutronPyPI
From 10.0.0 · fixed in 10.0.2-1.1
- neutronPyPI
fixed in 7.2.0-12.1; From 8.0.0 · fixed in 8.3.0-11.1; From 9.0.0 · fixed in 9.3.1-2.1; From 10.0.0 · fixed in 10.0.2-1.1