Synopsis

Moderate: openstack-cinder security update

Type/Severity

Security Advisory: Moderate

Topic

An update for OpenStack Block Storage (cinder) is now available for Red Hat OpenStack Platform 13 (Queens).

Red Hat Product Security has rated this update as having a security impact
of Moderate. A Common Vulnerability Scoring System (CVSS) base score, which
gives a detailed severity rating, is available for each vulnerability from
the CVE link(s) in the References section.

Description

OpenStack Block Storage (cinder) manages block storage mounting and the
presentation of such mounted block storage to instances. The backend
physical storage can consist of local disks, or Fiber Channel, iSCSI, and
NFS mounts attached to Compute nodes. In addition, Block Storage supports
volume backups, and snapshots for temporary save and restore operations.
Programmatic management is available via Block Storage's API.

Security Fix(es):

• Improper handling of ScaleIO backend credentials (CVE-2020-10755)

For more details about the security issue(s), including the impact, a CVSS score, and other related information, refer to the CVE page(s) listed in the References section.

Bug Fix(es):

• Before this update, FC live migration was failing. With this update, the correct device information is now sent to os-brick for FC for the corresponding host. Also, the device is now removed from the correct masking view when the live migration process has failed on the Compute node. (BZ#1841157)
• Before this update, the 3PAR driver did not look at the `_name_id` field for a possible volume ID, which caused volumes to be unusable after a live migration. With this update, the driver is now aware of the `_name_id` field as an alternative location for the volume ID, and live migrated volumes now work as expected. (BZ#1841866)
• Before this update, the internal temporary snapshot, created during async migration when creating a volume from a snapshot, was not being deleted from the VNX storage.

For example, if we create a new volume, V2, from snapshot S1, which we created from volume V1, an internal temporary snapshot, S2, is created from copying S1. V1 now has two snapshots, S1 and S2. Although we delete V1, V2 and S1 from OpenStack Block Storage (cinder), S2 is not deleted. This causes both V1 and S2 to remain on the VNX storage.

With this update, the temporary snapshot, S2, is deleted, and V1 can be successfully deleted. (BZ#1843196)

Solution

For details on how to apply this update, which includes the changes
described in this advisory, refer to:

https://access.redhat.com/articles/11258

Affected Products

• Red Hat OpenStack 13 x86_64
• Red Hat OpenStack for IBM Power 13 ppc64le

Fixes

• BZ - 1741730 - Concurrent cloning of the same volume fails with cinder NFS driver when using cinder backed glance images
• BZ - 1812988 - Partial cleanup after failed image to volume conversions
• BZ - 1841157 - Dell EMC PowerMax Cinder driver fixes for backward compatibility and FC LIve Migration.
• BZ - 1842748 - CVE-2020-10755 openstack-cinder: Improper handling of ScaleIO backend credentials
• BZ - 1843088 - Creating image-volume cache on NFS backend fails
• BZ - 1843196 - [Backport][OSP13] VNX: delete the LUN from VNX backend
• BZ - 1870569 - Rebase openstack-cinder to 8641eed

CVEs

• CVE-2020-10755

References