CVE Vulnerabilities

CVE-2016-8032

Improper Access Control

Published: Mar 31, 2017 | Modified: Jul 12, 2017
CVSS 3.x
7.3
HIGH
Source:
NVD
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
CVSS 2.x
4.4 MEDIUM
AV:L/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

Software Integrity Attacks vulnerability in Intel Security Anti-Virus Engine (AVE) 5200 through 5800 allows local attackers to bypass local security protection via a crafted input file.

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
Anti-malware_scan_engine Mcafee 5500 5500
Anti-malware_scan_engine Mcafee 5300 5300
Anti-malware_scan_engine Mcafee 5200 5200
Anti-malware_scan_engine Mcafee 5800 5800
Anti-malware_scan_engine Mcafee 5800 5800
Anti-malware_scan_engine Mcafee 5600 5600
Anti-malware_scan_engine Mcafee 5400 5400
Anti-malware_scan_engine Mcafee 5600 5600
Anti-malware_scan_engine Mcafee 5500 5500
Anti-malware_scan_engine Mcafee 5700 5700
Anti-malware_scan_engine Mcafee 5200 5200
Anti-malware_scan_engine Mcafee 5600 5600
Anti-malware_scan_engine Mcafee 5300 5300
Anti-malware_scan_engine Mcafee 5400 5400
Anti-malware_scan_engine Mcafee 5300 5300
Anti-malware_scan_engine Mcafee 5800 5800
Anti-malware_scan_engine Mcafee 5700 5700
Anti-malware_scan_engine Mcafee 5200 5200
Anti-malware_scan_engine Mcafee 5500 5500
Anti-malware_scan_engine Mcafee 5400 5400
Anti-malware_scan_engine Mcafee 5700 5700

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