CVE-2020-7302
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 · uneditedUnrestricted Upload of File with Dangerous Type in McAfee Data Loss Prevention (DLP) ePO extension prior to 11.5.3 allows authenticated attackers to upload malicious files to the DLP case management section via lack of sanity checking.
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 confidenceUnrestricted file upload vulnerability in McAfee Data Loss Prevention (DLP) ePO extension versions prior to 11.5.3 allows authenticated attackers to upload files of dangerous types to the DLP case management section due to missing sanity checking on uploaded files.
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
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:L
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 if McAfee DLP ePO extension is installedLocate the DLP ePO extension within the ePolicy Orchestrator console under the EPO tree, or check the installed extensions via the ePO server management interface.Affected if The DLP ePO extension is present in the environment.
-
Determine the installed DLP ePO extension versionAccess the ePO server console, navigate to the DLP extension details page, or use the ePO API to query the extension version information.Affected if The version displayed is lower than 11.3.28, between 11.4.0 and 11.4.199, or between 11.5.0 and 11.5.2.
-
Verify DLP case management functionality is accessibleCheck if the DLP Case Management section is available in the ePO console. This is typically found under the DLP menu in the ePolicy Orchestrator interface.Affected if The DLP Case Management feature is enabled and accessible to users.
-
Confirm user access to DLP case management upload featureReview the ePO user permissions and role assignments to determine which users or groups have access to the file upload capability within the DLP Case Management section.Affected if Non-administrator or untrusted users have access to upload files in the DLP Case Management section.
A user is affected if the DLP ePO extension version falls within the vulnerable ranges (11.3.0-11.3.27, 11.4.0-11.4.199, or 11.5.0-11.5.2) AND the DLP Case Management functionality with file upload is accessible to authenticated users.
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 which implements proper file type validation. If immediate upgrade is not possible, restrict access to the DLP case management functionality to only trusted administrators.
- Consultation2.0 h
- Implementation3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7302 — 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-7302 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