Knowledge Center

McAfee Security Bulletin: SIEM ESM, ESMREC, and ESMLM updates fix authentication bypass vulnerability
Security Bulletins ID:   SB10137
Last Modified:  4/7/2017


First Published: 10/21/2015
 Impact of Vulnerability:  Authentication Bypass (CWE-592)
 OS Command Injection (CWE-78)
 CVE Numbers:  CVE-2015-8024
 Severity Rating:  High
 Base / Overall CVSS v2  Scores:  9.3/8.4
 Base / Overall CVSS v3  Scores:  9.8/9.3
 Recommendations:  Install or update to SIEM ESM 9.5.0MR8 or 9.4.2MR9
 Security Bulletin  Replacement:  None
 Affected Software:  SIEM ESM 9.5.0MR7, 9.4.2MR8, 9.3.2MR18 and earlier releases. SIEM versions prior  to 9.3.0 are unaffected.
 Location of Updated  Software:  http://www.mcafee.com/us/downloads/downloads.aspx

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:


A specially crafted username can bypass SIEM ESM authentication (password is not validated) if the ESM is configured to use Active Directory or LDAP authentication sources. This can result in the attacker gaining NGCP (master user) access to the ESM.
This update resolves an issue where the login username is mishandled.

McAfee Enterprise Security Manager (ESM), Enterprise Security Manager/Log Manager (ESMLM), and Enterprise Security Manager/Receiver (ESMREC) 9.3.x before 9.3.2MR19, 9.4.x before 9.4.2MR9, and 9.5.x before 9.5.0MR8, when configured to use Active Directory or LDAP authentication sources, allow remote attackers to bypass authentication by logging in with the username "NGCP|NGCP|NGCP;" and any password.
Authentication Bypass
OS Command Injection
Affected Components:
  • SIEM ESM, ESMREC, and ESMLM (9.5.0, 9.4.2, 9.3.2)


For the latest SIEM ESM release, refer to KB83418.

This issue was also addressed in the October 2015 ESM Maintenance Releases listed in the table below. McAfee recommends that you update your installation to these (or later) ESM versions at your earliest convenience.

If you are unable to install the Maintenance Release immediately, you can work around this issue by disabling all Active Directory and LDAP authentication sources in the ESM.

NOTE: ESM local authentication is not affected by this vulnerability.

To obtain the Maintenance Release for your SIEM version, go to the Product Downloads site and download one of the following:
Product Type Version File Name Release Date
SIEM ESM 9.5.0 Maintenance Release 9.5.0MR8 ESS_Update_9.5.0MR7.signed.tgz
October 19, 2015
SIEM ESM 9.4.2 Maintenance Release 9.4.2MR9 ESS_Update_9.4.2.signed.tgz
October 21, 2015
SIEM ESM 9.3.2   Maintenance Release 9.3.2MR19 ESS_Update_9.3.2.signed.tgz
October 19, 2015

Download and Installation Instructions
See KB56057 for instructions on how to download McAfee products, documentation, security updates, patches, 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.

Product Specific Notes

Product Exposures
  • The NGCP (master) account is accessible to any attacker with network access to the ESM if Active Directory or LDAP authentication is enabled.


McAfee strongly recommends you install the available patches. If you cannot, consider disabling Active Directory and LDAP authentication sources in the ESM user management configuration as a temporary workaround.


No vulnerability detection signatures are available.


McAfee credits Claudio Cinquino from Quantum Leap SRL for reporting this flaw.

Frequently Asked Questions (FAQs)

How do I know whether 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 task bar.
  2. Select Open Console.
  3. In the console, select Action Menu.
  4. In the Action Menu, select Product Details. The product version is displayed.
For ePO / Server products:
Use the following instructions for server-based products:
  • Check the version and build of ePO that is installed. For more information on how to check the version, see: KB52634.
  • Or, create a query in ePO for the product version of the product installed within your organization.
For Appliances:
Use the following instructions for appliance-based products:
  1. Open the Administrator's User Interface (UI).
  2. Click the About link. The product version is displayed.
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, please visit the CVSS website at: http://www.first.org/cvss/.

When calculating CVSS v2 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 successful exploitation of the issue being scored.

CVSS v3 scoring is in final review as of March 2015. CVSS v2 will be replaced with CVSS v3 when v3 is fully approved.
What are the CVSS scoring metrics that have been used?

 Base Score 9.3
 Related exploit range (AccessVector) Network (N)
 Attack complexity (AccessComplexity) Medium (M)
 Level of authentication needed (Authentication) None (N)
 Confidentiality impact Complete (C)
 Integrity impact Complete (C)
 Availability impact Complete (C)
 Temporal Score (Overall) 8.4
 Availability of exploit (Exploitability) Functional Exploit Exists (F)
 Type of fix available (RemediationLevel) Workaround (W)
 Level of verification that vulnerability exists (ReportConfidence) Confirmed (C)

NOTE: The below CVSS version 2.0 vector was used to generate this score.

Alternate CVSS v3 Scoring:
 Base Score 9.8
 Attack Vector (AV) Network (N)
 Attack Complexity (AC) Low (L)
 Privileges Required (PR) None (N)
 User Interaction (UI) None (N)
 Scope (S) Unchanged (U)
Confidentiality (C) High (H)
Integrity (I) High (H)
Availability (A) High (H)
 Temporal Score (Overall) 9.3
 Exploitability (E) Functional (F)
 Remediation Level (RL) Workaround (W)
 Report Confidence (RC) Confirmed (C)

NOTE: The below CVSS version 3.0 (beta) vector was used to generate this score.

Where can I find a list of all security bulletins or how do I report a product vulnerability?
To find a list of all security bulletins, or if you have information about a security issue or vulnerability with a McAfee product, please visit our product security website at: http://www.mcafee.com/us/threat-center/product-security-bulletins.aspx.


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 foregoing 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 cancelled 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.