CVE-2019-3633
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 a carefully constructed message sent to DLPe which bypasses DLPe internal checks and 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 · high confidenceBuffer overflow vulnerability in McAfee Data Loss Prevention (DLPe) for Windows 11.x allows a local user to send a specially crafted message that bypasses internal validation checks, causing DLPe to read unallocated memory and trigger a Windows blue screen (BSOD). The vulnerability exists in versions prior to 11.3.2.8.
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.
-
Confirm McAfee DLPe is installedOpen Windows Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product' in PowerShell, and look for 'McAfee Data Loss Prevention Endpoint' or 'DLPe' in the installed programs listAffected if McAfee Data Loss Prevention Endpoint appears in installed programs
-
Identify the installed DLPe versionCheck the program version via Help > About in the DLPe console, or query the Windows Registry under HKLM\SOFTWARE\McAfee\DLPe for the Version value, or use McAfee ePO if centrally managedAffected if The reported version is 11.3.0 through 11.3.2.81 (any version prior to 11.3.2.8 within the 11.3.x line)
-
Verify the DLPe service is runningOpen Services.msc and locate the 'McAfee DLPe Service' or 'McAfee DLP Endpoint' service, or run 'Get-Service | Where-Object {$_.DisplayName -like "*DLPe*"}' in PowerShellAffected if The DLPe service is installed and currently running (the vulnerability requires the service to be active to trigger the buffer overflow)
-
Review Windows Event Logs for DLPe-related crashesOpen Event Viewer > Windows Logs > System, filter for Event ID 1001 (Bugcheck) or search for sources containing 'DLPe' or 'McAfee' around the time of any blue screen eventsAffected if Event logs show bugcheck (BSOD) events with DLPe or McAfee DLP as the faulting module
A system is affected if McAfee Data Loss Prevention Endpoint version 11.3.0 through 11.3.2.81 is installed and the DLPe service is running, as this matches the vulnerable version range prior to the 11.3.2.8 patch.
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
Apply vendor patch by upgrading McAfee DLPe to version 11.3.2.8 or later. Since this is a local-only vulnerability requiring authenticated access, ensure proper access controls and monitor for unusual DLPe service behavior.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3633 — 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-3633 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