CVE-2019-3640
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 · uneditedUnprotected Transport of Credentials in ePO extension in McAfee Data Loss Prevention 11.x prior to 11.4.0 allows remote attackers with access to the network to collect login details to the LDAP server via the ePO extension not using a secure connection when testing LDAP connectivity.
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 confidenceMcAfee Data Loss Prevention 11.x prior to 11.4.0 contains an ePO extension that transmits LDAP server credentials in cleartext without encryption when testing LDAP connectivity. An attacker with network access can intercept these credentials during the LDAP connection test operation.
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>= 11.0.0, <= 11.4.0CVSS 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
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify McAfee DLP versionCheck the installed McAfee DLP version via Windows Add/Remove Programs, or query the registry key HKLM\SOFTWARE\McAfee\DLP, or access ePolicy Orchestrator console and check the DLP extension versionAffected if Installed version is 11.0.0 through 11.4.0 (any version prior to 11.4.0)
-
Confirm ePO extension is in useVerify that ePolicy Orchestrator (ePO) is managing the DLP installation by checking ePO console or registry for ePO agent communicationAffected if ePO is managing the DLP installation and the version is vulnerable
-
Identify LDAP configurationCheck the McAfee DLP policy settings for LDAP server configurations under the DLP ePO extension settings or LDAP integration moduleAffected if LDAP integration is configured and the DLP version is vulnerable
-
Determine LDAP test functionality accessReview whether users with administrative privileges can trigger the LDAP connectivity test operation through the DLP ePO extension interfaceAffected if LDAP test functionality is accessible and the DLP version is in the vulnerable range
You are affected if McAfee DLP version is 11.0.0 through 11.4.0 and LDAP connectivity testing is performed through the ePO extension, as credentials will be transmitted in cleartext.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade McAfee DLP to version 11.4.0 or later which implements secure credential transport for LDAP connectivity testing. If immediate upgrade is not possible, ensure network segmentation and monitoring to limit exposure of LDAP credentials.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3640 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-3640 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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