dbcve.org
Data Loss Prevention EndpointApplication · Mcafee

CVE-2022-2330

MEDIUM · 6.5 CVSS v3.1 Published 2022-08-30
Fix available
A fix is available. Upgrade to 11.6.600.212 / 11.9.100 or later.
See remediation →
71/100
Remediation priority · Elevated
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
Improper Restriction of XML External Entity Reference vulnerability in DLP Endpoint for Windows prior to 11.9.100 allows a remote attacker to cause the DLP Agent to access a local service that the attacker wouldn't usually have access to via a carefully constructed XML file, which the DLP Agent doesn't parse correctly.

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 confidence

This is an XML External Entity (XXE) injection vulnerability in DLP Endpoint for Windows versions prior to 11.9.100. The DLP Agent improperly parses XML files, allowing a remote attacker to craft a malicious XML document that causes the agent to access local services the attacker normally wouldn't have permission to reach.

MitigationUpgrade DLP Endpoint for Windows to version 11.9.100 or later to receive the security patch. As a temporary control, restrict the ability of the DLP Agent to access sensitive local services and monitor for anomalous XML processing activity.

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.600.212>= 11.9.0, < 11.9.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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

  1. Verify McAfee DLP Endpoint for Windows is installed
    Open Programs and Features or check the system for McAfee Data Loss Prevention Endpoint agent. On the system, run 'reg query "HKLM\SOFTWARE\McAfee\DLP"' or check for the DLP Agent service.
    Affected if McAfee DLP Endpoint for Windows is not found on the system, this CVE does not apply.
  2. Determine the installed DLP Endpoint version
    Open the DLP Endpoint console, check the agent properties in the ePO console, or run 'reg query "HKLM\SOFTWARE\McAfee\DLP" /v Version' to retrieve the installed version number.
    Affected if The version is less than 11.6.600.212, OR greater than or equal to 11.9.0 but less than 11.9.100. Compare your version against these ranges.
  3. Confirm the DLP Agent XML parsing feature is active
    Check if the DLP Endpoint Agent service (often named 'McAfee DLPE' or similar) is running and check the DLP policy configuration for XML content inspection or data discovery rules that process XML files.
    Affected if The DLP Agent service is running and XML parsing rules are enabled; the XXE vulnerability requires the agent to process XML content.
  4. Inspect DLP Endpoint configuration for XML handling policies
    In the DLP Endpoint policy settings, look for content inspection rules that scan XML documents, DLP rules with XML file type filters, or data discovery profiles that parse XML-based files.
    Affected if XML file parsing or XML content inspection rules are configured and active; the vulnerability requires XML files to be processed by the agent.

If McAfee DLP Endpoint for Windows is installed with a version in the range < 11.6.600.212 or >= 11.9.0 to < 11.9.100, and the DLP Agent XML parsing feature is enabled, the environment is affected by this XXE 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.600.212 / 11.9.100 or later
Fixed in 11.6.600.21211.9.100
Interim mitigation

Upgrade DLP Endpoint for Windows to version 11.9.100 or later to receive the security patch. As a temporary control, restrict the ability of the DLP Agent to access sensitive local services and monitor for anomalous XML processing activity.

Recommended fix High confidence

DLP Endpoint 11.9.100 or later (or 11.6.600.212 or later for the 11.6.x branch)

  1. Obtain the fixed DLP Endpoint agent version (11.9.100 or later, or 11.6.600.212 or later) from the Trellix support portal at kcm.trellix.com
  2. Test the upgrade in a non-production environment to ensure compatibility with existing systems
  3. Deploy the updated DLP Endpoint agent to production Windows endpoints using your enterprise deployment tool (e.g., Trellix ePO, SCCM, or Group Policy)
  4. Verify the agent upgrade was successful by checking the DLP Endpoint version on managed systems
  5. Confirm the XXE vulnerability is remediated by verifying the DLP Agent no longer processes external entity references in XML files

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

Fix this in Data Loss Prevention Endpoint Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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