dbcve.org
Mcafee Enterprise Security ManagerApplication · Mcafee

CVE-2015-8024

HIGH · 9.3 CVSS v2.0 Published 2015-12-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

McAfee Enterprise Security Manager products contain an authentication bypass vulnerability when configured to use Active Directory or LDAP authentication sources. Attackers can gain unauthorized access by using the specific username 'NGCP|NGCP|NGCP;' with any password, effectively bypassing the LDAP/AD authentication check.

MitigationApply vendor-supplied patches (9.3.2MR19, 9.4.2MR9, 9.5.0MR8 or later) to all affected ESM, ESMLM, and ESMREC installations. If patches cannot be applied immediately, consider disabling AD/LDAP authentication and using local authentication as a temporary workaround.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mcafee Enterprise Security ManagerApplication
Affected:= 9.3.0= 9.3.1= 9.3.2= 9.4.0= 9.4.1= 9.4.2= 9.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed ESM version
    Access the ESM console or check the product About/Version information panel. Alternatively, check the installation directory for version files or use the system's package manager if available.
    Affected if The installed version matches 9.3.0, 9.3.1, 9.3.2, 9.4.0, 9.4.1, 9.4.2, or 9.5.0 exactly.
  2. Verify if Active Directory or LDAP authentication is enabled
    Navigate to the ESM administrative settings and locate the Authentication or User Management configuration section. Look for authentication source settings that include AD or LDAP integration.
    Affected if AD or LDAP authentication sources are configured and active.
  3. Review authentication and audit logs for the specific bypass username
    Search the ESM security logs, authentication logs, or SIEM event logs for login attempts using the username pattern 'NGCP|NGCP|NGCP;'. Check both failed and successful authentication events.
    Affected if Any log entries showing login attempts with this specific username are found, indicating active exploitation attempts.

You are affected if your ESM version is 9.3.0 through 9.5.0 AND Active Directory/LDAP authentication is configured, regardless of whether you see exploitation attempts in logs.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied patches (9.3.2MR19, 9.4.2MR9, 9.5.0MR8 or later) to all affected ESM, ESMLM, and ESMREC installations. If patches cannot be applied immediately, consider disabling AD/LDAP authentication and using local authentication as a temporary workaround.

Recommended fix High confidence

Apply the appropriate MR patch: 9.3.2MR19 for 9.3.x, 9.4.2MR9 for 9.4.x, or 9.5.0MR8 for 9.5.x

  1. 1. Identify the currently installed ESM version via the product UI or system information
  2. 2. For ESM 9.3.x versions: Apply patch 9.3.2MR19 or later
  3. 3. For ESM 9.4.x versions: Apply patch 9.4.2MR9 or later
  4. 4. For ESM 9.5.x versions: Apply patch 9.5.0MR8 or later
  5. 5. Obtain patches from McAfee KnowledgeBase (kc.mcafee.com) using the article related to CVE-2015-8024
  6. 6. Apply the patch following McAfee standard patch deployment procedures
  7. 7. Verify the patch was applied successfully by checking the version number
  8. 8. Test authentication with Active Directory/LDAP sources to confirm the vulnerability is remediated
Caveat Standard patch deployment; review McAfee release notes for any configuration changes required post-patch

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mcafee Enterprise Security Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-8024 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-8024 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data