OpenStack Dashboard (Horizon) provides administrators and users with a
graphical interface to access, provision, and automate cloud-based
resources.
Two security issues were discovered in the Horizon dashboard and are
addressed in this update:
Red Hat would like to thank the OpenStack Project for reporting the
CVE-2015-3219 issue. Upstream acknowledges Nikita Konovalov from Mirantis
as the original reporter of CVE-2015-3219.
Additionally, the following non-security issues are addressed:
It was impossible to associate a floating IP address to a port for an
instance. This occurred if the gateway router was not in the same tenant as
the instance but was attached to a network shared across tenants because
only ports within the tenant were used to find reachable gateway routers.
(BZ#1187992)
If two or more regions were configured in Horizon, then the User, Help,
and Current Project links would no longer work and the region selector
was in the wrong location in the UI. (BZ#1189887)
A load balancer monitor was erroneously displayed as associated with
every tenant in every pool. The load balancer monitor was not actually
associated with any tenants, but the improper display prevented users
from using the Horizon dashboard to create a tenant association.
(BZ#1196249)
When logging into the Horizon dashboard, Horizon sends a query to Nova to
update usage statistics. One of the calls would erroneously query deleted
virtual machines; if there were thousands of deleted virtual machines, the
CPU usage for Nova would spike and the Nova process could crash.
(BZ#1243301)
The network profile was not supported by Cisco N1KV ML2 drivers. This
profile has been removed to maintain Horizon compatibility with the Cisco
driver. (BZ#1246690)
A neutron attribute extension was renamed from profile_id to profile for
networks and ports. This caused create operations for networks and ports to
fail from the dashboard since the dashboard was still using the attribute
name n1kv:profile_id rather than n1kv:profile.(BZ#1248367)
If a virtual machine instance failed to launch, then the stale port
assignments were left in the configuration rather than being cleaned up.
(BZ#1249228)
All python-django-horizon users are advised to upgrade to these updated
packages, which correct these issues.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
RedHat | 7 | noarch | openstack-dashboard | < 2014.2.3-7.el7ost | openstack-dashboard-2014.2.3-7.el7ost.noarch.rpm |
RedHat | 7 | noarch | openstack-dashboard-theme | < 2014.2.3-7.el7ost | openstack-dashboard-theme-2014.2.3-7.el7ost.noarch.rpm |
RedHat | 7 | noarch | python-django-horizon | < 2014.2.3-7.el7ost | python-django-horizon-2014.2.3-7.el7ost.noarch.rpm |
RedHat | 7 | noarch | python-django-horizon-doc | < 2014.2.3-7.el7ost | python-django-horizon-doc-2014.2.3-7.el7ost.noarch.rpm |