CVE-2020-7305
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 · uneditedPrivilege escalation vulnerability in McAfee Data Loss Prevention (DLP) ePO extension prior to 11.5.3 allows a low privileged remote attacker to create new rule sets via incorrect validation of user credentials.
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 confidencePrivilege escalation vulnerability in McAfee Data Loss Prevention ePO extension allows authenticated low-privileged remote attackers to create new rule sets due to improper validation of user credentials in versions prior to 11.5.3.
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.28>= 11.4.0, < 11.4.200>= 11.5.0, < 11.5.3CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Confirm McAfee DLP ePO extension is installedLog into the McAfee ePO console and navigate to Server Settings > Extensions, or check the ePO server registry under HKLM\SOFTWARE\Network Associates\ePolicy Orchestrator for DLP extension entriesAffected if The DLP extension is not listed or not present in the ePO console
-
Identify the installed DLP ePO extension versionIn the ePO console, go to Menu > Software > Product Deployment, or check the extension manifest file in the ePO installation directory under \extensions\DLPEPO\. Verify the exact version number displayedAffected if The version falls within any of these ranges: 11.3.0 through 11.3.27, 11.4.0 through 11.4.199, or 11.5.0 through 11.5.2
-
Verify the ePO management interface is remotely accessibleConfirm that the ePO console web interface is exposed to network access, rather than only accessible locally on the ePO server. Check ePO Server Settings > Communication > Agents for external connectivity statusAffected if The ePO console is reachable from network locations, enabling remote attackers to authenticate
-
Review ePO user accounts for low-privileged usersIn the ePO console, navigate to Menu > Users > User Management, or query the ePO database for users with roles other than Administrator. Look for users assigned to the DLP Operator or DLP Viewer roles with limited permissionsAffected if Non-administrator user accounts exist in ePO who could exploit the improper credential validation to create rule sets
You are affected if McAfee DLP ePO extension is installed with a version below 11.5.3 (specifically 11.3.0-11.3.27, 11.4.0-11.4.199, or 11.5.0-11.5.2) and the ePO console is network-accessible with low-privileged accounts present.
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.2811.4.20011.5.3
Upgrade McAfee DLP ePO extension to version 11.5.3 or later to remediate the vulnerability.
- Consultation3.0 h
- Implementation2.0 h
- Testing6.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 $3,552.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7305 — 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-2020-7305 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