CVE Vulnerabilities

CVE-2016-0757

Improper Access Control

Published: Apr 13, 2016 | Modified: Feb 12, 2023
CVSS 3.x
4.3
MEDIUM
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
CVSS 2.x
4 MEDIUM
AV:N/AC:L/Au:S/C:N/I:P/A:N
RedHat/V2
3.5 LOW
AV:N/AC:M/Au:S/C:N/I:P/A:N
RedHat/V3
Ubuntu
MEDIUM

OpenStack Image Service (Glance) before 2015.1.3 (kilo) and 11.0.x before 11.0.2 (liberty), when show_multiple_locations is enabled, allow remote authenticated users to change image status and upload new image data by removing the last location of an image.

Weakness

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

Affected Software

Name Vendor Start Version End Version
Image_registry_and_delivery_service_(glance) Openstack 11.0.0 (including) 11.0.0 (including)
Image_registry_and_delivery_service_(glance) Openstack 11.0.1 (including) 11.0.1 (including)
Image_registry_and_delivery_service_(glance) Openstack 2015.1.2 (including) 2015.1.2 (including)
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 6 RedHat openstack-glance-0:2014.1.5-5.el6ost *
Red Hat Enterprise Linux OpenStack Platform 5.0 (Icehouse) for RHEL 7 RedHat openstack-glance-0:2014.1.5-5.el7ost *
Red Hat Enterprise Linux OpenStack Platform 6.0 (Juno) for RHEL 7 RedHat openstack-glance-0:2014.2.3-4.el7ost *
Red Hat Enterprise Linux OpenStack Platform 7.0 (Kilo) for RHEL 7 RedHat openstack-glance-0:2015.1.2-2.el7ost *
Glance Ubuntu precise *
Glance Ubuntu trusty *
Glance Ubuntu wily *

Extended Description

Access control involves the use of several protection mechanisms such as:

When any mechanism is not applied or otherwise fails, attackers can compromise the security of the product by gaining privileges, reading sensitive information, executing commands, evading detection, etc. There are two distinct behaviors that can introduce access control weaknesses:

Potential Mitigations

  • Compartmentalize the system to have “safe” areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
  • Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References