First published: Mon Aug 31 2015(Updated: )
It was reported that a vulnerability was found in Neutron. By changing the device owner of an instance's port right after it is created, an authenticated user may prevent application of firewall rules and so avoid IP anti-spoofing controls. All Neutron setups using the ML2 plugin or a plugin that relies on the security groups AMQP API are affected. All Neutron setups using the ML2 plugin or a plugin that relies on the security groups AMQP API are affected. Vulnerability affects versions through 2014.2.3 and 2015.1 versions through 2015.1.1 Acknowledgements: Red Hat would like to thank the OpenStack project for reporting this issue. Upstream acknowledges Kevin Benton from Mirantis as the original reporter.
Credit: secalert@redhat.com secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
OpenStack Neutron | =2014.2.3 | |
OpenStack Neutron | =2015.1.0 | |
OpenStack Neutron | =2015.1.1 | |
pip/neutron | <7.0.0 | 7.0.0 |
=2014.2.3 | ||
=2015.1.0 | ||
=2015.1.1 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-5240 has a medium severity rating due to its potential to bypass firewall rules and IP anti-spoofing controls.
To fix CVE-2015-5240, upgrade OpenStack Neutron to version 7.0.0 or later.
CVE-2015-5240 affects OpenStack Neutron versions 2014.2.3, 2015.1.0, and 2015.1.1.
An authenticated user can exploit CVE-2015-5240 by altering the device owner of an instance's port immediately after creation.
The implications of CVE-2015-5240 include the potential for unauthorized bypass of network security features.