Bugzilla – Bug 964138
VUL-0: CVE-2016-0757: openstack-glance: Glance image status manipulation through locations removal
Last modified: 2016-06-01 10:22:21 UTC
Created attachment 663740 [details] Patches This is an advance warning of a vulnerability discovered in OpenStack, to give you, as downstream stakeholders, a chance to coordinate the release of fixes and reduce the vulnerability window. Please treat the following information as confidential until the proposed public disclosure date. Title: Glance image status manipulation through locations removal Reporter: Erno Kuvaja (HPE) Products: Glance Affects: <=2015.1.2, >=11.0.0 <= 11.0.1 Description: Erno Kuvaja from HPE reported a vulnerability in Glance. By removing the last location of an image, an authenticated user may change the image status back to queued and may be able to upload new image data resulting in a broken Glance's immutability promise. A malicious tenant may exploit this flaw to silently replace image data it owns, regardless of the original creator or the visibility settings. Only setups with show_multiple_locations enabled (not default) are affected. Note: The proposed fix prevents the removal of the last location of an image so that an active image is always available. This action was previously incorrectly allowed and the fix might break some users who are relying on the false assumption that it would be ok to replace the data of existing image in the special case that the multiple locations has been configured. Proposed patch: See attached patches. Unless a flaw is discovered in them, these patches will be merged to master/mitaka, stable/kilo and stable/liberty on the public disclosure date. CVE: CVE-2016-0757 Proposed public disclosure date/time: CRD: 2016-02-03 1500 UTC
bugbot adjusting priority
according to /opt/dell/chef/cookbooks/glance/templates/default/glance-api.conf.erb: show_multiple_locations = <%= node[:glance][:show_storage_location] %> we expose this option to users (defaulting to False) even in the UI as Expose Backend Store Location so we are potentially affected, but not by default.
is public: https://bugs.launchpad.net/glance/+bug/1525915 https://review.openstack.org/#/q/topic:bug/1525915
Doesn't impact Cloud 5 (we don't use this option), and Cloud 6 already has the fix. Can we close this?
yes