CVE-2022-3338
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 · uneditedAn 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.
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 confidenceAn External XML entity (XXE) vulnerability in McAfee ePolicy Orchestrator (ePO) prior to version 5.10 Update 14 allows unauthenticated remote attackers to inject malicious XML entities through the API by mimicking Agent Handler calls, potentially leading to Server Side Request Forgery (SSRF).
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< 5.10.0= 5.10.0CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify ePO server versionLocate the ePO installation and check the version number in the product console or installation files. Common locations include the ePO console 'About' page or registry keys under HKLM\Software\McAfee\ePolicy OrchestratorAffected if The installed version is 5.10.0 or any version prior to 5.10.0 (versions below 5.10.0)
-
Confirm ePO version is below 5.10 Update 14Compare the installed version against the fixed version 5.10.0 Update 14. If the version cannot be determined or shows 5.10.0 without update 14, consider it potentially affectedAffected if Version is 5.10.0 without Update 14, or any version lower than 5.10.0
-
Verify Agent Handler API service is accessibleCheck if the ePO Agent Handler service is running and exposed on the network. The vulnerability exists in the API endpoint that mimics Agent Handler calls, typically accessible on port 443 or 8443Affected if The Agent Handler API service is running and network-accessible without additional authentication controls
-
Review API endpoint exposureDetermine if the ePO API endpoint (used for Agent Handler communication) is exposed to untrusted networks. This endpoint accepts XML input and is where the XXE injection occursAffected if The API endpoint is reachable from untrusted or external networks without network segmentation or authentication proxies
A system is affected if ePO version is 5.10.0 or any version below 5.10.0, and the Agent Handler API endpoint is accessible to potential attackers.
Generated from the published advisory. Verify against your own configuration.
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 · scoped5.10.0
Update ePO to version 5.10 Update 14 or later to patch the XXE vulnerability. If immediate patching is not feasible, consider restricting API access through network segmentation or web application firewall rules.
ePO 5.10.0 with Update 14 applied (or later update)
- Back up the ePolicy Orchestrator database before applying any updates
- Download ePO 5.10 Update 14 from the Trellix downloads portal (kcm.trellix.com or authorized channel)
- Apply the update through the ePO console or via the ePO update installer following Trellix documentation
- Verify the update was applied successfully by checking the ePO version information
- Test critical ePO functionalities to ensure normal operation after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3338 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-3338 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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