dbcve.org
Data Loss Prevention EndpointApplication · Mcafee

CVE-2021-31849

HIGH · 7.2 CVSS v3.1 Published 2021-11-01
Fix available
A fix is available. Upgrade to 11.6.400 / 11.7.100 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
SQL injection vulnerability in McAfee Data Loss Prevention (DLP) ePO extension prior to 11.7.100 allows a remote attacker logged into ePO as an administrator to inject arbitrary SQL into the ePO database through the user management section of the DLP ePO extension.

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

SQL injection vulnerability in McAfee Data Loss Prevention (DLP) ePO extension's user management section allows an authenticated ePO administrator to inject arbitrary SQL commands into the underlying ePO database. The vulnerability exists in versions prior to 11.7.100.

MitigationUpgrade McAfee DLP ePO extension to version 11.7.100 or later to obtain the vendor patch that addresses the SQL injection 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 Prevention EndpointApplication
Affected:>= 11.6.0, < 11.6.400>= 11.7.0, < 11.7.100

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

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

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

  1. Verify McAfee DLP ePO extension is installed
    Log into the ePO console and navigate to Server Settings > Extensions > Installed Extensions, or check the extension management page for any installed extensions with name containing 'Data Loss Prevention' or 'DLPE'.
    Affected if The DLP ePO extension is not listed in installed extensions.
  2. Determine the installed version of the DLP ePO extension
    In the ePO console, click on the DLP extension entry in the Extensions page to view its version details. The version is typically displayed as a four-part number (e.g., 11.7.0.x).
    Affected if Unable to retrieve version information from the ePO console.
  3. Compare the installed version against affected ranges
    Review the version number found in the previous step. Affected versions are: 11.6.0 through 11.6.399 (inclusive) AND 11.7.0 through 11.7.99 (inclusive). Versions 11.6.400 and above, and 11.7.100 and above, are not affected.
    Affected if The installed version falls within 11.6.0 to 11.6.399 or 11.7.0 to 11.7.99.
  4. Confirm user management functionality is accessible
    In the ePO console, navigate to the DLP section and verify that the User Management or Administration sub-section is accessible. This is the specific component where the SQL injection vulnerability exists.
    Affected if The user management section is accessible in the DLP ePO extension interface.

If the McAfee DLP ePO extension is installed and its version falls within 11.6.0-11.6.399 or 11.7.0-11.7.99 with the user management section accessible, the environment is affected by this SQL injection vulnerability.

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.

dbcve · scoped
Upgrade available Upgrade to 11.6.400 / 11.7.100 or later
Fixed in 11.6.40011.7.100
Interim mitigation

Upgrade McAfee DLP ePO extension to version 11.7.100 or later to obtain the vendor patch that addresses the SQL injection vulnerability.

Recommended fix High confidence

11.6.400 or 11.7.100 (or later)

  1. 1. Confirm current DLP ePO extension version through ePO console under Menu > Software > Software Catalog or Menu > Server Settings > Data Loss Prevention
  2. 2. Download the fixed DLP ePO extension version (11.6.400 or 11.7.100 or later) from the McAfee ServicePortal at support.mcafee.com or kc.mcafee.com
  3. 3. Navigate to Menu > Software > Software Management > Extensions in ePO console
  4. 4. Import the new DLP ePO extension package using the Import Extension option
  5. 5. Follow the on-screen upgrade wizard to complete the installation
  6. 6. Verify the upgrade was successful by checking the DLP ePO extension version in the console
Caveat Enterprise software upgrades should be tested in a non-production environment before deployment; review McAfee release notes for version-specific compatibility and migration notes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Data Loss Prevention Endpoint Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-31849 — 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-2021-31849 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