McAfee Endpoint Security CVE-2019-3652 Local Code Injection Vulnerability



Date Discovered

October 11, 2019


McAfee Endpoint Security is prone to a vulnerability that lets attackers inject and execute arbitrary code. Successfully exploiting this issue may allow attackers to inject and execute arbitrary code. This may lead to other attacks. McAfee Endpoint Security (ENS) versions prior to 10.6.1 October 2019 Update and 10.5.5 October 2019 Update are vulnerable.

Technologies Affected

  • McAfee Endpoint Security 10.5.0
  • McAfee Endpoint Security 10.5.1
  • McAfee Endpoint Security 10.5.2
  • McAfee Endpoint Security 10.5.3
  • McAfee Endpoint Security 10.5.4
  • McAfee Endpoint Security 10.5.5
  • McAfee Endpoint Security 10.6.0
  • McAfee Endpoint Security 10.6.1


Permit local access for trusted individuals only. Where possible, use restricted environments and restricted shells.
Ensure that only trusted users have local, interactive access to affected computers.

Run all software as a nonprivileged user with minimal access rights.
To reduce the impact of latent vulnerabilities, always run nonadministrative software as an unprivileged user with minimal access rights.

Do not follow links provided by unknown or untrusted sources.
Web users should be cautious about following links to websites that are provided by unfamiliar or suspicious sources. Filtering HTML from emails may help remove a possible vector for transmitting malicious links to users.

Implement multiple redundant layers of security.
Since this issue may be leveraged to execute code, we recommend memory-protection schemes, such as nonexecutable stack/heap configurations and randomly mapped memory segments. This tactic may complicate exploits of memory-corruption vulnerabilities.

Updates are available. Please see the references or vendor advisory for more information.



Russell Wells from DRS

© 1995- Symantec Corporation

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from


The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Security Response, and are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.