CVE-2019-3622
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 · uneditedFiles or Directories Accessible to External Parties in McAfee Data Loss Prevention (DLPe) for Windows 11.x prior to 11.3.0 allows authenticated user to redirect DLPe log files to arbitrary locations via incorrect access control applied to the DLPe log folder allowing privileged users to create symbolic links.
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 (DLPe) for Windows 11.x prior to 11.3.0 contains an incorrect access control vulnerability in the DLPe log folder. An authenticated user can create symbolic links to redirect DLPe log files to arbitrary locations, potentially enabling privilege escalation or information disclosure.
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, < 11.1.200>= 11.2.000, < 11.3.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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/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.
-
Identify DLPe installationCheck if McAfee Data Loss Prevention Endpoint is installed on the Windows system by looking for the DLPe service or checking Programs and Features for 'McAfee Data Loss Prevention Endpoint'Affected if DLPe is installed on the system
-
Determine DLPe versionOpen Windows Registry and navigate to HKLM\SOFTWARE\McAfee\DLPe (or check the product GUI under Help > About) to find the installed version numberAffected if The installed version is 11.0.x through 11.1.200.x, or 11.2.000.x through 11.2.x.x (any version below 11.3.0)
-
Locate DLPe log folderFind the default log directory, typically at C:\Program Files\McAfee\Data Loss Prevention\log or check the LogsPath value in the registry under HKLM\SOFTWARE\McAfee\DLPe\ConfigurationAffected if The log folder exists and is accessible to authenticated users
-
Verify log folder permissionsRight-click the DLPe log folder, go to Properties > Security, and check which users or groups have Write or Create Files permissions on the folderAffected if Authenticated users (non-admin) have permission to create files or symbolic links in the log directory
The system is affected if McAfee DLPe version is below 11.3.0 and the log folder allows authenticated users to create symbolic links or write to the directory.
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.1.20011.3.0
Upgrade McAfee DLPe for Windows to version 11.3.0 or later to remediate this vulnerability.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3622 — 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-3622 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