CVE Vulnerabilities

CVE-2016-0241

Improper Access Control

Published: Oct 22, 2016 | Modified: Nov 28, 2016
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
6.5 MEDIUM
AV:N/AC:L/Au:S/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

IBM Security Guardium Database Activity Monitor 8.2 before p310, 9.x through 9.5 before p700, and 10.x through 10.1 before p100 allows remote authenticated users to spoof administrator accounts by sending a modified login request over HTTP.

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
Security_guardium_database_activity_monitor Ibm 8.2 (including) 8.2 (including)
Security_guardium_database_activity_monitor Ibm 9.0 (including) 9.0 (including)
Security_guardium_database_activity_monitor Ibm 9.1 (including) 9.1 (including)
Security_guardium_database_activity_monitor Ibm 9.5 (including) 9.5 (including)
Security_guardium_database_activity_monitor Ibm 10.0 (including) 10.0 (including)
Security_guardium_database_activity_monitor Ibm 10.1 (including) 10.1 (including)
Security_guardium_database_activity_monitor Ibm 10.01 (including) 10.01 (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