First Published: June 20, 2019
| Impact of Vulnerability: |
Improper Access Control (CWE-287)
Permissions, Privileges, and Access Control (CWE-264) |
| CVE ID: |
None |
| Severity Rating: |
Medium |
| CVSS v3 Base/Temporal Scores: |
5.0 / 4.7 |
| Recommendations: |
Deploy product updates as they are made available. |
| Security Bulletin Replacement: |
None |
| Affected Software: |
See the Remediation table below |
| Location of updated software: |
Product Downloads site |
To receive email notification when this article is updated, click Subscribe on the right side of the page. You must be logged on to subscribe.
Article contents:
Vulnerability Description
Windows Kernel APIs return stale and inconsistent FILE_OBJECT paths, which enable an adversary to bypass Windows operating system Process attribute verification.
There are hotfixes, updates, and Maintenance Releases addressing this issue for the impacted products. These releases are listed below.
Product Vulnerability Status
We are only listing impacted products on Windows as this issue is operating system specific. Any Windows product not shown in the table below or listed in the
Product-Specific Notes section, is under assessment.
Remediation
To remediate this issue, go to the
Product Downloads site, and download the applicable product update/hotfix files. The table shows the first release that contained the remediation. Any releases after the version/date shown are protected.
| Product |
Versions |
Type |
Release Date |
| Anti-Virus Engine |
6010 |
Minor |
May 14, 2019 |
| Application Control |
8.2.1 Update 3 |
Update |
March 6, 2019 |
| Data Exchange Layer (DXL) (Messaging) |
4.0.0 Hotfix 8 |
Hotfix |
November 13, 2018 |
| DXL (Messaging) |
4.1.2 |
Update |
November 13, 2018 |
| DXL Broker (Messaging) |
5.0.1 Update 1 |
Update |
February 26, 2019 |
| DXL Client (Messaging) |
5.0.1 Update 2 |
Update |
February 26, 2019 |
| Endpoint Intelligence Agent (EIA) |
2.6.4 |
Update |
December 14, 2018 |
| Endpoint Security (ENS) |
10.6.1 July Update Repost |
Update |
August 13, 2019 |
| ENS |
10.5.5 July Update Repost |
Update |
August 13, 2019 |
| Groupshield Domino |
7.5.3 |
Hotfix |
March 6, 2018 |
| Groupshield Exchange |
8.6 Patch 1 |
Patch |
November 13, 2018 |
| GroupShield SharePoint |
3.5 Patch 1 |
Patch |
November 13, 2018 |
| Host Intrusion Prevention |
8.0 Patch 13 |
Patch |
August 13, 2019 |
| McAfee Active Response (MAR) |
2.3.0 Hotfix 4 |
Hotfix |
November 13, 2018 |
| MAR |
2.4.0 Hotfix 1 |
Hotfix |
November 27, 2018 |
| McAfee Agent |
5.6.1 |
Update |
May 14, 2019 |
| MVISION EDR |
3.0.0 |
Major |
March 27, 2019 |
| MVISION Endpoint |
1811 Update 2 |
Update |
January 8, 2019 |
| Real Protect |
1.1.0.4963 |
Update |
January 16, 2019 |
| Threat Intelligence Exchange Client for VirusScan Enterprise |
1.0.3 Hotfix 21090212 |
Hotfix |
February 12, 2019 |
| VirusScan Enterprise (VSE) |
8.8 Patch 12 |
Patch |
February 12, 2019 |
| VirusScan Enterprise for Storage |
8.8 Patch 12 |
Patch as part of VSE above |
February 12, 2019 |
Download and Installation Instructions
For instructions to download product updates and hotfixes, see
KB56057 - How to download Enterprise product updates and documentation. Review the Release Notes and the Installation Guide for instructions on how to install these updates. All documentation is available on the
Product Documentation site.
Product-Specific Notes
Anti-Virus Engine
Elective downloads were made available on May 15, 2019.
Automatic updates will be enabled from June 25, 2019.
The Anti-Virus Engine has been updated to use the MPT drivers when installed.
- For ENS, make sure that you have updated to the relevant versions and then wait for the auto-update on or after June 25, 2019.
- For VSE, customers need to update to the latest version of VSE and select the new Anti-Virus Engine manually for deployment.
- For command-line users of the Anti-Virus Engine, this issue does not affect scanning static files.
Data Loss Prevention Endpoint (DLP Endpoint) for Windows
DLP Endpoint is watching files to prevent loss of confidential information from the organization. It is not using information from running processes to find executable files to scan. As such it is not vulnerable.
Acknowledgments
We credit
Eoin Carroll,
Steve Hearnden, and
Cedric Cochin from our
Advanced Threat Research (ATR) team for reporting this flaw.
Frequently Asked Questions (FAQs)
How do I know if my product is vulnerable?
For Endpoint products:
Use the following instructions for endpoint or client-based products:
- Right-click on the McAfee tray shield icon on the Windows taskbar.
- Select Open Console.
- In the console, select Action Menu.
- In the Action Menu, select Product Details. The product version displays.
For ePO:
Use the following instructions for ePO:
Check the version and build of ePO that is installed. For information about how to check the version, see:
KB52634.
For Appliances:
Use the following instructions for Appliance-based products:
- Open the Administrator's User Interface (UI).
- Click the About link. 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, we've 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?
Process Reimaging security bypass in Microsoft Windows:
| Base Score |
5.0 |
| Attack Vector (AV) |
Local (L) |
| Attack Complexity (AC) |
Low (L) |
| Privileges Required (PR) |
Low (L) |
| User Interaction (UI) |
Required (R) |
| Scope (S) |
Unchanged (U) |
| Confidentiality (C) |
None (N) |
| Integrity (I) |
High (H) |
| Availability (A) |
None (N) |
| Temporal Score (Overall) |
4.7 |
| Exploitability (E) |
Proof-of-Concept (P) |
| Remediation Level (RL) |
Unavailable (U) |
| Report Confidence (RC) |
Confirmed (C) |
NOTE: The below CVSS version 3.0 vector was used to generate this score.
https://www.first.org/cvss/calculator/3.0#CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:N/E:P/RL:U/RC:C
Where can I find a list of all Security Bulletins?
All Security Bulletins are published on our Knowledge Center. 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 you?
If you have information about a security issue or vulnerability with a product, follow the instructions provided in KB95563 - Report a vulnerability.
How do you 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 our 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.
We only publish 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.
To view our PSIRT policy, see KB95564 - About PSIRT.
Resources
- 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 fields to have your password and instructions emailed to you.
Disclaimer
The information provided in this Security Bulletin is provided as is without warranty of any kind. We disclaim all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall we or our suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits, or special damages, even if we or our suppliers have been advised of the possibility of such damages. Some states don't 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 shouldn't 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 aren't 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 remain at our sole discretion and may be changed or canceled at any time.
