CVE-2019-3634
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 · uneditedBuffer overflow in McAfee Data Loss Prevention (DLPe) for Windows 11.x prior to 11.3.2.8 allows local user to cause the Windows operating system to "blue screen" via an encrypted message sent to DLPe which when decrypted results in DLPe reading unallocated memory.
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 · moderate confidenceBuffer overflow vulnerability in McAfee Data Loss Prevention (DLPe) for Windows 11.x prior to version 11.3.2.8. A local user can send a specially crafted encrypted message to DLPe that, when decrypted, causes the application to read from unallocated memory, resulting in a Windows blue screen (denial of service).
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.3.0, < 11.3.2.82CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
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 DLPe is installedCheck for the presence of McAfee Data Loss Prevention Endpoint by looking in Add/Remove Programs, or check for the DLPe installation directory (commonly in C:\Program Files\McAfee\DLPE or C:\Program Files\McAfee\Data Loss Prevention), or query the Windows registry under HKLM\SOFTWARE\McAfee\DLPEAffected if McAfee Data Loss Prevention Endpoint is not found on the system, the system is not affected
-
Identify the installed DLPe versionOpen the Windows Registry and navigate to HKLM\SOFTWARE\McAfee\DLPE\, or check the version information of the main DLPe executable file in the installation directory, or use the McAfee ePO console if available to view agent version informationAffected if The version cannot be determined or the product is not present
-
Compare version against vulnerable rangeReview the installed version number and compare it to the affected range: versions 11.3.0 through 11.3.2.81 are vulnerable. Version 11.3.2.8 and later are fixedAffected if The installed version is 11.3.0, 11.3.1.x, 11.3.2.0 through 11.3.2.81, or any 11.3.x version below 11.3.2.8
-
Confirm DLPe service is activeOpen Services.msc and verify the McAfee Data Loss Prevention Endpoint service status, or run 'sc query' for DLPe-related servicesAffected if DLPe is installed but the service is not running, the specific denial-of-service condition would not trigger even if the vulnerable version is present
The environment is affected if McAfee Data Loss Prevention Endpoint version 11.3.0 through 11.3.2.81 is installed and the DLPe service is active on a Windows system.
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 data11.3.2.82
Upgrade McAfee Data Loss Prevention (DLPe) for Windows to version 11.3.2.8 or later to resolve the buffer overflow vulnerability.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3634 — 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-3634 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