CVE-2022-3339
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 · uneditedA reflected cross-site scripting (XSS) vulnerability in ePO prior to 5.10 Update 14 allows a remote unauthenticated attacker to potentially obtain access to an ePO administrator's session by convincing the authenticated ePO administrator to click on a carefully crafted link. This would lead to limited access to sensitive information and limited ability to alter some information in ePO.
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 confidenceA reflected cross-site scripting (XSS) vulnerability in McAfee ePolicy Orchestrator (ePO) versions prior to 5.10 Update 14 allows a remote unauthenticated attacker to inject malicious JavaScript through a crafted URL. When an authenticated ePO administrator clicks the specially crafted link, the attacker's script executes in the administrator's browser context, enabling limited information disclosure and limited data modification within the ePO system.
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
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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.
-
Confirm ePO installation existsLook for the McAfee ePolicy Orchestrator service or check Program Files for the McAfee ePO folder. On Windows, check Services for 'McAfee ePolicy Orchestrator' or 'ePO' entries.Affected if ePO software is installed on the system
-
Identify installed ePO versionAccess the ePO console and navigate to Server Settings > Server Information, or check the registry key HKLM\SOFTWARE\McAfee\ePolicy Orchestrator\Installer for the Version value.Affected if Version cannot be determined or is less than 5.10.0
-
Compare version to affected rangeThe affected versions are any release less than 5.10.0 and the specific release 5.10.0. Note the exact version number found in the previous step.Affected if Installed version is 5.10.0 or any version below 5.10.0 (e.g., 5.9.x, 5.8.x, etc.)
-
Verify Update level for version 5.10.0If the base version reads exactly 5.10.0, check if Update 14 is applied. In the ePO console, look at the full version string which includes the update number (e.g., 5.10.0.14 would indicate Update 14).Affected if Running 5.10.0 without Update 14 applied
The environment is affected if the installed ePO version is 5.10.0 without Update 14 applied, or any version lower than 5.10.0.
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
Upgrade ePO to version 5.10 Update 14 or later. Until patching is feasible, train administrators to avoid clicking untrusted links and consider implementing URL filtering/monitoring on perimeter devices.
ePO 5.10 Update 14
- Identify current ePO version by navigating to Menu > Settings > Server Settings > ePolicy Orchestrator or checking the ePO console login page
- Download ePO 5.10 Update 14 from the Trellix support portal (kcm.trellix.com) using valid credentials
- Back up the ePO database and server configuration before upgrading
- Run the ePO 5.10 Update 14 installer and follow the on-screen prompts to complete the upgrade
- Verify successful installation by checking that the ePO version displays 5.10.0 with Update 14 applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-3339 — 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-3339 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