# CVE-2022-2330: XXE vulnerability in DLP Endpoint for Windows

> A remote attacker can exploit an XML parsing flaw in Trellix DLP Endpoint to access local services, potentially reading sensitive data or bypassing security controls.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-3mjp-86xg-ff9v

## What is CVE-2022-2330?

CVE-2022-2330 is a medium-severity vulnerability in Trellix DLP Endpoint for Windows, published on 30 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2022-2330?

It affects 1 product.


Products: Mcafee Data Loss Prevention Endpoint.

## How do I fix CVE-2022-2330?

No fix has been published for CVE-2022-2330 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-2330 being exploited?

There is no known exploitation of CVE-2022-2330 in the wild and no public exploit code.

## Other vulnerabilities in Trellix DLP Endpoint for Windows

- [CVE-2021-31848](https://insights.sbomify.com/CVE-2021-31848/): Data Loss Prevention (DLP) ePO extension - Cross site scripting (XSS) (high 8.4)
- [CVE-2021-31849](https://insights.sbomify.com/CVE-2021-31849/): Data Loss Prevention (DLP) ePO extension - SQL injection (high 8.4)
- [CVE-2021-31844](https://insights.sbomify.com/CVE-2021-31844/): Local Privilege Escalation in McAfee DLP Endpoint for Windows (high 8.2)
- [CVE-2021-23887](https://insights.sbomify.com/CVE-2021-23887/): Privilege escalation in McAfee DLP Endpoint for Windows (high 7.8)
- [CVE-2016-8012](https://insights.sbomify.com/CVE-2016-8012/): Privilege escalation in Data Loss Prevention Endpoint (DLPe) (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-2330 and fix it if it is affected.

What it is: CVE-2022-2330 is a medium-severity vulnerability in Trellix DLP Endpoint for Windows, published on 30 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-2330 in the wild and no public exploit code.

Affected product: Trellix DLP Endpoint for Windows. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-2330/ (Markdown: https://insights.sbomify.com/CVE-2022-2330/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-2330
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-2330
- OSV: https://osv.dev/vulnerability/CVE-2022-2330

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-2330/
Summaries are generated and may contain mistakes; the official description above is the record.
