Loading...

Knowledge Center


McAfee Security Bulletin - Endpoint Security for Windows update fixes two vulnerabilities (CVE-2019-3652 and CVE-2019-3653)
Security Bulletins ID:   SB10299
Last Modified:  10/11/2019

Summary

First Published: October 8, 2019
 
 Impact of Vulnerability: CVE-2019-3652 - Code Injection (CWE-94)
CVE-2019-3653 - Improper Access Control (CWE-287)
 CVE ID: CVE-2019-3652
CVE-2019-3653
 Severity Rating: CVE-2019-3652: Medium
CVE-2019-3653: Medium
 CVSS v3 Base/Temporal Scores: CVE-2019-3652: 5.0 / 4.3
CVE-2019-3653: 5.0 / 4.3
 Recommendations: Install or update to one of the following Endpoint Security (ENS) versions:
  • ENS 10.6.1 October 2019 Update
  • ENS 10.5.5 October 2019 Update
 Security Bulletin Replacement: None
 Affected Software: ENS for Windows:
  • 10.6.x
  • 10.5.x
 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 on to subscribe.

Article contents: Vulnerability Description
This Security Bulletin covers two vulnerabilities in ENS. To exploit these vulnerabilities, an attacker would need to gain access to the system.
  1. CVE-2019-3652 - ENS code injection in EPSetup.exe
    Code Injection vulnerability in EPSetup.exe in McAfee Endpoint Security (ENS) prior to 10.6.1 October 2019 Update allows local user to get their malicious code installed by the ENS installer via code injection into EPSetup.exe by an attacker with access to the installer.
    https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-3652  
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3652
     
  2. CVE-2019-3653 - ESConfig Tool access not controlled
    Improper access control vulnerability in configuration tool in McAfee Endpoint Security (ENS) prior to 10.6.1 October 2019 Update allows local user to disable security features via unauthorized use of the configuration tool.
    https://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2019-3653  
    https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2019-3653
Remediation
To remediate these issues:
  • Customers using ENS 10.6.x should update to ENS 10.6.1 October 2019 Update.
  • Customers using ENS 10.5.x should update to ENS 10.5.5 October 2019 Update, or upgrade to ENS 10.6.1 October 2019 Update.
Go to the Product Downloads site, and download the applicable product update files:
 
Product Version Type Release Date Restart Needed?
ENS for Windows  10.6.1 October 2019 Update Update October 8, 2019 No
ENS for Windows 10.5.5 October 2019 Update Update October 8, 2019 No
 
Download and Installation Instructions
See KB56057 for instructions to download McAfee products, documentation, updates, and hotfixes. See the Release Notes and the Installation Guide, which you can download from the Documentation tab, for instructions to install these updates.
Acknowledgments
CVE-2019-3652: McAfee credits Russell Wells from DRS for reporting this flaw.
CVE-2019-3653: McAfee credits Donny Maasland from Fox-IT for reporting this flaw.
Frequently Asked Questions (FAQs)
How do I know if my McAfee product is vulnerable?
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. Click 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, which 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-2019-3652 - ENS code injection in EPSetup.exe
     
    Base Score 5.0
    Attack Vector (AV) Local (L)
    Attack Complexity (AC) High (H)
    Privileges Required (PR) Low (L)
    User Interaction (UI) Required (R)
    Scope (S) Changed (C)
    Confidentiality (C) Low (L)
    Integrity (I) Low (L)
    Availability (A) Low (L)
    Temporal Score (Overall) 4.3
    Exploitability (E) Proof-of-Concept (P)
    Remediation Level (RL) Official Fix (O)
    Report Confidence (RC) Reasonable (R)
     
    NOTE: The below CVSS version 3.0 vector was used to generate this score.
    https://nvd.nist.gov/cvss/v3-calculator?vector=AV:L/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:L/E:P/RL:O/RC:R
     
  2. CVE-2019-3653 - ESConfig Tool access not controlled
     
    Base Score 5.0
    Attack Vector (AV) Local (L)
    Attack Complexity (AC) High (H)
    Privileges Required (PR) Low (L)
    User Interaction (UI) Required (R)
    Scope (S) Unchanged (U)
    Confidentiality (C) High (H)
    Integrity (I) Low (L)
    Availability (A) None (N)
    Temporal Score (Overall) 4.3
    Exploitability (E) Proof-of-Concept (P)
    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.
    https://nvd.nist.gov/cvss/v3-calculator?vector=AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:L/A:N/E:P/RL:O/RC:C
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?
McAfee's 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 make sure 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.
Resources
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.
Disclaimer
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.