Knowledge Center

McAfee Security Bulletin - Application and Change Control update fixes Bypass Application Control issue with simple DLL or through an ASP.NET (CVE-2018-6668, CVE-2018-6669)
Security Bulletins ID:   SB10261
Last Modified:  12/20/2018


First Published: December 18, 2018
 Impact of Vulnerability: Application Protections Bypass (CWE-592)
 CVE ID: CVE-2018-6668, CVE-2018-6669
 Severity Rating: Medium
 CVSS v3 Base/Temporal Scores: CVE-2018-6668: 6.1 / 5.8
CVE-2018-6669: 6.3 / 6.0
 Recommendations: Install or update to McAfee Application and Change Control (MACC) Application 8.0.0 and MACC ePO extension 8.0.0 or later
 Security Bulletin Replacement: None
 Affected Software: MACC 7.0.1 and all earlier versions
 Location of updated software: http://www.mcafee.com/us/downloads/downloads.aspx
To receive email notification when this Security Bulletin is updated, click Subscribe on the right side of the page. You must be logged in to subscribe.
Article contents: Vulnerability Description
Bypass using a DLL or ASP.NET in MACC 7.0.1 and earlier allows remote attackers to perform arbitrary command execution via a command-line utility.

This version of software mitigates the bypass vulnerability on PowerShell and similar interpreters.
For detailed information, see: https://adsecurity.org/?p=2604
Previous Knowledge Base article: KB86405 (Section 3.2.1)
  1. CVE-2018-6668   
    Bypass Application Control with simple DLL
    A whitelist bypass vulnerability in McAfee Application Control / Change Control 7.0.1 and before allows execution bypass, for example, with simple DLL trough interpreters such as PowerShell.
  2. CVE-2018-6669
    Bypass Application Control through an ASP.NET form
    A whitelist bypass vulnerability in McAfee Application Control / Change Control 7.0.1 and before allows a remote or local user to execute blacklisted files through an ASP.NET form.
To remediate this issue, go to the Product Downloads site, and download the applicable product update file:
Product Type File Name Release Date
MACC Release 8.0.0 December 16, 2016
To remediate the problem, interpreter execution (in other words, PowerShell) in Application Control 8.0 is only allowed when running scripts files (for example, .ps1 files) but interactive mode must be disabled.

To disable this mode, after you install or upgrade MACC, you must configure MACC through ePO to disable interactive mode for console-based processes in the Application Control rules. The steps are:
  1. Open the ePO console.
  2. Go to Application Control Rules (Windows), Execution Control.
  3. Click Add.
  4. In Action, click Block interactive mode for console-based process.
  5. In the Process Name field, type the interpreter that you want to block, in other words, PowerShell.exe.
If you need to allow the interactive mode of PowerShell (or similar interpreters), you can specify certain conditions to execute the interpreter, including the parameters: process name, path, command-line arguments, parent process name, and user name. This feature allows you to continue using interactive mode for console-based processes but controlling specific scenarios.

Download and Installation Instructions
See KB56057 for instructions on how to download McAfee products, documentation, updates, and hotfixes. Review the Release Notes and the Installation Guide, which you can download from the Documentation tab, for instructions on how to install these updates.
Frequently Asked Questions (FAQs)
How do I know if my McAfee product is vulnerable or not?
For Endpoint products:
Use the following instructions for endpoint or client-based products:
  1. Right-click on the McAfee tray shield icon on the Windows taskbar.
  2. Select Open Console.
  3. In the console, select Action Menu.
  4. In the Action Menu, select Product Details. The product version displays.
What is CVSS?
CVSS, or Common Vulnerability Scoring System, is the result of the National Infrastructure Advisory Council's effort to standardize a system of assessing the criticality of a vulnerability. This system offers an unbiased criticality score between 0 and 10 that customers can use to judge how critical a vulnerability is and plan accordingly. For more information, visit the CVSS website at: http://www.first.org/cvss/.
When calculating CVSS scores, McAfee has adopted a philosophy that fosters consistency and repeatability. Our guiding principle for CVSS scoring is to score the exploit under consideration by itself. We consider only the immediate and direct impact of the exploit under consideration. We do not factor into a score any potential follow-on exploits that might be made possible by the successful exploitation of the issue being scored.
What are the CVSS scoring metrics?
  1. CVE-2018-6668: Bypass Application Control with simple DLL
    Base Score 6.1
    Attack Vector (AV) Local (L)
    Attack Complexity (AC) Low (L)
    Privileges Required (PR) Low (L)
    User Interaction (UI) None (N)
    Scope (S) Unchanged (U)
    Confidentiality (C) Low (L)
    Integrity (I) None (N)
    Availability (A) High (H)
    Temporal Score (Overall) 5.8
    Exploitability (E) High (H)
    Remediation Level (RL) Official Fix (O)
    Report Confidence (RC) Confirmed (C)
    NOTE: The below CVSS version 3.0 vector was used to generate this score.
  2. CVE-2018-6669: Bypass Application Control through an ASP.NET
    Base Score 6.3
    Attack Vector (AV) Adjacent (A)
    Attack Complexity (AC) Low (L)
    Privileges Required (PR) Low (L)
    User Interaction (UI) None (N)
    Scope (S) Unchanged (U)
    Confidentiality (C) Low (L)
    Integrity (I) None (N)
    Availability (A) High (H)
    Temporal Score (Overall) 6.0
    Exploitability (E) High (H)
    Remediation Level (RL) Official Fix (O)
    Report Confidence (RC) Confirmed (C)
    NOTE: The below CVSS version 3.0 vector was used to generate this score.
Where can I find a list of all Security Bulletins?
All Security Bulletins are published on our external PSIRT website at http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx > Security Bulletins. Security Bulletins are retired (removed) once a product is both End of Sale and End of Support (End of Life).
How do I report a product vulnerability to McAfee?
If you have information about a security issue or vulnerability with a McAfee product, visit the McAfee PSIRT website for instructions at http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx > Report a Security Vulnerability.
How does McAfee respond to this and any other reported security flaws?
Our key priority is the security of our customers. If a vulnerability is found within any of McAfee software or services, we work closely with the relevant security software development team to ensure the rapid and effective development of a fix and communication plan.
McAfee only publishes Security Bulletins if they include something actionable such as a workaround, mitigation, version update, or hotfix. Otherwise, we would simply be informing the hacker community that our products are a target, putting our customers at greater risk. For products that are updated automatically, a non-actionable Security Bulletin might be published to acknowledge the discoverer.
View our PSIRT policy on the McAfee PSIRT website at http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx > About PSIRT.
To contact Technical Support, log on to the ServicePortal and go to the Create a Service Request page at https://support.mcafee.com/ServicePortal/faces/serviceRequests/createSR:
  • If you are a registered user, type your User ID and Password, and then click Log In.
  • If you are not a registered user, click Register and complete the required fields. Your password and logon instructions will be emailed to you.
The information provided in this Security Bulletin is provided as is without warranty of any kind. McAfee disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall McAfee or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if McAfee or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the preceding limitation may not apply.
Any future product release dates mentioned in this Security Bulletin are intended to outline our general product direction, and they should not be relied on in making a purchasing decision. The product release dates are for information purposes only, and may not be incorporated into any contract. The product release dates are not a commitment, promise, or legal obligation to deliver any material, code, or functionality. The development, release, and timing of any features or functionality described for our products remains at our sole discretion and may be changed or canceled at any time.

Rate this document

Beta Translate with

Select a desired language below to translate this page.

Glossary of Technical Terms

 Highlight Glossary Terms

Please take a moment to browse our Glossary of Technical Terms.