Date: 19 February 2016
Click here for printable version
Click here for PGP verifiable version
-----BEGIN PGP SIGNED MESSAGE-----
AUSCERT External Security Bulletin Redistribution
Moderate: openstack-heat bug fix and security advisory
19 February 2016
AusCERT Security Bulletin Summary
Publisher: Red Hat
Operating System: Red Hat Enterprise Linux Server 7
Impact/Access: Denial of Service -- Existing Account
Access Confidential Data -- Existing Account
CVE Names: CVE-2015-5295
Comment: This advisory references vulnerabilities in products which run on
platforms other than Red Hat. It is recommended that administrators
running openstack-heat check for an updated version of the software
for their operating system.
- --------------------------BEGIN INCLUDED TEXT--------------------
- -----BEGIN PGP SIGNED MESSAGE-----
Red Hat Security Advisory
Synopsis: Moderate: openstack-heat bug fix and security advisory
Advisory ID: RHSA-2016:0266-01
Product: Red Hat Enterprise Linux OpenStack Platform
Advisory URL: https://rhn.redhat.com/errata/RHSA-2016-0266.html
Issue date: 2016-02-18
CVE Names: CVE-2015-5295
Updated openstack-heat packages that fix one security issue and resolve
various bugs are now available for Red Hat Enterprise Linux OpenStack
Platform 7.0 (Kilo) for RHEL 7.
Red Hat Product Security has rated this update as having Moderate security
impact. Common Vulnerability Scoring System (CVSS) base scores, which give
detailed severity ratings, are available for each vulnerability from the
CVE links in the References section.
2. Relevant releases/architectures:
Red Hat Enterprise Linux OpenStack Platform 7.0 for RHEL 7 - noarch
OpenStack Orchestration (heat) is a template-driven engine used to specify
and deploy configurations for Compute, Storage, and OpenStack Networking.
A vulnerability was discovered in the OpenStack Orchestration
service (heat), where a specially formatted template could be used to
trick the heat-engine service into opening a local file. Although the
file contents are never disclosed to the end user, an OpenStack-
authenticated attacker could use this flaw to cause a denial of service
or determine whether a given file name is present on the server.
This issue was discovered by Steven Hardy of Red Hat.
This update has the following known issue:
* By default, the number of created heat-engine workers match the number of
cores on the undercloud. However, if there is only one core, there is only
one heat-engine worker, and this causes deadlocks when creating the
overcloud stack. A single heat-engine worker is not enough to launch an
overcloud stack. Workaround: The undercloud must have at least two
(virtual) cores. For virtual deployments, this should be two vCPUs,
regardless of cores on the baremetal host. Otherwise, you can uncomment the
num_engine_workers line in /etc/heat/heat.conf, and restart openstack-
This update also fixes the following bugs:
* When a stack update fails, Orchestration stores a merged environment
file. Previously, with an interrupted update, the merged environment file
was not written, any resources already created that had new type aliases in
the environment could not have their types resolved, and the failed stack
could not be updated. This patch now catches any exceptions that occur, and
ensures that the stack can now be updated. (BZ#1290950)
* Previously, stack updates resulted in an OS::Neutron::Port resource
being replaced when the property values were changed in the following
- The network property referred to the same network, but by name instead
of UUID, or by UUID instead of name.
- Specifying the network using the 'network' property instead of the
deprecated 'network_id' property, or using the deprecated 'network_id'
property instead of the network property.
This issue has been resolved. (BZ#1291845)
* This update resolves an issue that caused the deployment of Orchestration
templates to fail during resource validation. Network IDs are now correctly
* Previously, using the Orchestration API actions > check call removed
output values from the existing stack (using either CLI or dashboard). This
broke stack updates and other operations depending on stack output values
after operation execution. This issue has been resolved. (BZ#1299257)
* Upgrades of overclouds from Red Hat Enterprise Linux OpenStack
Platform 7.2 to 7.3 failed with the error
controller_swift_proxy_memcaches_v6 not assigned". This issue has been
* Previously, when resource metadata was requested from Orchestration, all
attribute values were fetched, even though this data was not returned by
the API. This meant at least one pointless ReST API call to the OpenStack
service, and "404 Not Found" messages accumulated in both heat-engine and
nova-api logs. With this update, Orchestration no longer calculates
attribute values when only the metadata for a resource is requested.
* Previously, the "heat-manage purge_delete" cron job on the undercloud
failed when attempting to purge the raw_template table. This patch fixes
the raw_template purge query on MySQL, and handles stack tags before
removing stacks which resolves the issue and also removes some race
conditions where incorrect data was being deleted.(BZ#1306444)
Before applying this update, ensure all previously released errata relevant
to your system have been applied.
Red Hat Enterprise Linux OpenStack Platform 7 runs on Red Hat Enterprise
The Red Hat Enterprise Linux OpenStack Platform 7 Release Notes contain the
* An explanation of the way in which the provided components interact to
form a working cloud computing environment.
* Technology Previews, Recommended Practices, and Known Issues.
* The channels required for Red Hat Enterprise Linux OpenStack Platform 7,
including which channels need to be enabled and disabled.
The Release Notes are available at:
- - -notes/release-notes
This update is available through 'yum update' on systems registered through
Red Hat Subscription Manager. For more information about Red Hat
Subscription Manager, see:
5. Bugs fixed (https://bugzilla.redhat.com/):
1280094 - Uncaught exceptions can leave stacks hanging UPDATE_IN_PROGRESS
1288207 - Heat is unable to delete stack's resources if a 'port' name is given to a resource and not a UUID.
1290949 - rhel-osp-director: re-ran the deployment command: "Stack failed with status: resources.Controller: MessagingTimeout: resources: Timed out waiting for a reply to message ID 863d0fbc6ce24cd288074d901d1a6e64 ERROR: openstack Heat Stack update failed."
1290950 - rhel-osp-director: update 7.0->7.2 and 7.2 >7.3 fails StackValidationFailed: Unknown resource Type : OS::TripleO::NodeTLSCAData (*include-password or export HEAT_INCLUDE_PASSWORD=1)
1291845 - when not using network isolation, after an update from GA to latest release the apis try to reach the old public_virtual_ip
1292152 - Heat template fails in validation started with OSP7
1298295 - CVE-2015-5295 openstack-heat: Vulnerability in Heat template validation leading to DoS
1299257 - heat API: actions->check removes stack output values.
1299613 - rhel-osp-director: Scale-up Ceph from 1 to 3 fails, when Overcloud is deployed with SSL (resources.EndpointMap: Timed out) .
1300847 - rhel-osp-director: Overcloud update from 7.2-> 7.3 fails "resources.SwiftDevicesAndProxyConfig: Property controller_swift_proxy_memcaches_v6 not assigned "
1302828 - Hooks can remain set after a stack operation is stopped
1304854 - Metadata polling unnecessarily calls Nova
1304935 - Heat logs gigabytes of boring, worthless stuff
1306444 - DB Purge of raw_template fails on constraint from resources.current_template_id
6. Package List:
Red Hat Enterprise Linux OpenStack Platform 7.0 for RHEL 7:
These packages are GPG signed by Red Hat for security. Our key and
details on how to verify the signature are available from
The Red Hat security contact is <email@example.com>. More contact
details at https://access.redhat.com/security/team/contact/
Copyright 2016 Red Hat, Inc.
- -----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
- -----END PGP SIGNATURE-----
- --------------------------END INCLUDED TEXT--------------------
You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to firstname.lastname@example.org
and we will forward your request to the appropriate person.
NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members. As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.
NOTE: This is only the original release of the security bulletin. It may
not be updated when updates to the original are made. If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.
Contact information for the authors of the original document is included
in the Security Bulletin above. If you have any questions or need further
information, please contact them directly.
Previous advisories and external security bulletins can be retrieved from:
Australian Computer Emergency Response Team
The University of Queensland
Internet Email: email@example.com
Facsimile: (07) 3365 7031
Telephone: (07) 3365 4417 (International: +61 7 3365 4417)
AusCERT personnel answer during Queensland business hours
which are GMT+10:00 (AEST).
On call after hours for member emergencies only.
-----BEGIN PGP SIGNATURE-----
-----END PGP SIGNATURE-----