CVE Vulnerabilities

CVE-2015-1937

Improper Access Control

Published: May 30, 2015 | Modified: Nov 30, 2016
CVSS 3.x
N/A
Source:
NVD
CVSS 2.x
7.5 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

IBM PowerVC 1.2.0.x through 1.2.0.4, 1.2.1.x through 1.2.1.2, and 1.2.2.x through 1.2.2.2 does not require authentication for the ceilometer NoSQL database, which allows remote attackers to read or write to arbitrary database records, and consequently obtain administrator privileges, via a session on port 27017.

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
Powervc Ibm 1.2.0.0 (including) 1.2.0.0 (including)
Powervc Ibm 1.2.0.1 (including) 1.2.0.1 (including)
Powervc Ibm 1.2.0.2 (including) 1.2.0.2 (including)
Powervc Ibm 1.2.0.3 (including) 1.2.0.3 (including)
Powervc Ibm 1.2.0.4 (including) 1.2.0.4 (including)
Powervc Ibm 1.2.1.0 (including) 1.2.1.0 (including)
Powervc Ibm 1.2.1.1 (including) 1.2.1.1 (including)
Powervc Ibm 1.2.1.2 (including) 1.2.1.2 (including)
Powervc Ibm 1.2.2.0 (including) 1.2.2.0 (including)
Powervc Ibm 1.2.2.1 (including) 1.2.2.1 (including)
Powervc Ibm 1.2.2.2 (including) 1.2.2.2 (including)

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