CVE-2019-3595
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 · uneditedImproper Neutralization of Special Elements used in a Command ('Command Injection') in ePO extension in McAfee Data Loss Prevention (DLP) 11.x prior to 11.3.0 allows Authenticated Adminstrator to execute arbitrary code with their local machine privileges via a specially crafted DLP policy, which is exported and opened on the their machine. In our checks, the user must explicitly allow the code to execute.
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 confidenceCommand injection vulnerability in McAfee DLP's ePO extension allows an authenticated administrator to create a specially crafted DLP policy that, when exported and opened on their local machine, executes arbitrary code with local machine privileges. The user must explicitly allow the code to execute, somewhat limiting exploitability.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:U/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 installed McAfee DLP versionCheck the installed version of McAfee Data Loss Prevention Endpoint through the ePO console, Windows Programs and Features, or the DLP agent status dialog. The version is typically visible in the agent properties or ePO server console under the DLP extension details.Affected if The installed version falls within the affected ranges: 11.0 through 11.1.199, or 11.2.000 through 11.2.x (any version below 11.3.0).
-
Verify ePO extension is present and enabledLog into the ePO console and navigate to Menu > Server Settings > Extensions. Locate the McAfee DLP ePO extension and confirm its status. Alternatively, check the extension directory on the ePO server for the DLP ePO package files.Affected if The DLP ePO extension is installed and enabled, which is required for the policy export functionality that contains the vulnerability.
-
Confirm DLP policy export capability is accessibleIn the ePO console, navigate to the DLP policy management section and verify if the policy export feature is available to administrators. Check user role permissions to see if authenticated administrators can export DLP policies.Affected if Policy export functionality is accessible to authenticated administrators, which is the attack vector for this command injection.
-
Review recent policy export activityExamine ePO audit logs or DLP incident logs for any policy export events, particularly those originating from administrator accounts around the time frame of the CVE disclosure. Check for exports of policies that may have been opened on local machines.Affected if Suspicious policy exports are found that were not initiated by legitimate administrators, or exported policies were subsequently opened on local machines.
A system is affected if McAfee DLP Endpoint version is below 11.3.0, the ePO extension is enabled, and administrators have the ability to export DLP policies which can then trigger arbitrary code execution when opened locally.
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 Data Loss Prevention (DLP) to version 11.3.0 or later to resolve the command injection vulnerability in the ePO extension.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-3595 — 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-3595 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