dbcve.org
Data Loss PreventionApplication · Mcafee

CVE-2020-7304

HIGH · 7.6 CVSS v3.1 Published 2020-08-13
Fix available
A fix is available. Upgrade to 11.3.28 / 11.4.200 or later.
See remediation →
78/100
Remediation priority · High
Zero-click

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 · unedited
Cross site request forgery vulnerability in McAfee Data Loss Prevention (DLP) ePO extension prior to 11.5.3 allows authenticated remote attacker to embed a CRSF script via adding a new label.

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 confidence

CSRF vulnerability in McAfee Data Loss Prevention ePO extension allows authenticated remote attackers to embed malicious CSRF scripts by adding new labels, potentially enabling unauthorized actions on behalf of authenticated users.

MitigationUpgrade McAfee DLP ePO extension to version 11.5.3 or later to remediate the vulnerability.

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
Data Loss PreventionApplication
Affected:>= 11.3.0, < 11.3.28>= 11.4.0, < 11.4.200>= 11.5.0, < 11.5.3

CVSS 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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
Low

CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm McAfee DLP ePO extension is installed
    Access the ePO console and navigate to Menu > Server Settings > Extensions. Look for the McAfee Data Loss Prevention extension in the list of installed extensions.
    Affected if The extension is not listed in the ePO console extensions page
  2. Identify the installed DLP ePO extension version
    In the ePO console Extensions page, locate the McAfee Data Loss Prevention entry and record the version number shown in the extension details pane.
    Affected if Unable to retrieve a version number from the extension details
  3. Compare version against affected ranges
    Compare the installed version to these affected ranges: 11.3.0 through 11.3.27, 11.4.0 through 11.4.199, and 11.5.0 through 11.5.2. Any version matching these ranges is vulnerable.
    Affected if Installed version is 11.3.x where x is less than 28, OR 11.4.x where x is less than 200, OR 11.5.x where x is less than 3

The environment is affected if the McAfee DLP ePO extension version falls within 11.3.0-11.3.27, 11.4.0-11.4.199, or 11.5.0-11.5.2.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 11.3.28 / 11.4.200 / 11.5.3 or later
Fixed in 11.3.2811.4.20011.5.3
Interim mitigation

Upgrade McAfee DLP ePO extension to version 11.5.3 or later to remediate the vulnerability.

Fix this in Data Loss Prevention Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,780
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-7304 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-7304 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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