CVE-2022-0857
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 McAfee Enterprise ePolicy Orchestrator (ePO) prior to 5.10 Update 13 allows a remote attacker to potentially obtain access to an ePO administrator's session by convincing the attacker 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 due to the area of the User Interface the vulnerability is present in.
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 confidenceReflected XSS vulnerability in McAfee ePolicy Orchestrator web interface allows injection of malicious JavaScript through crafted URLs. When an authenticated ePO administrator clicks a manipulated link, the payload executes in their session context, enabling session hijacking with limited access to sensitive information and limited ability to modify certain ePO settings.
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.
-
Verify ePolicy Orchestrator is installedCheck for ePO installation directory (typically C:\Program Files\McAfee\ePolicy Orchestrator or /opt/McAfee/ePolicy Orchestrator) or look for ePO services running on the systemAffected if ePO is not found on the system, this CVE does not apply
-
Determine installed ePO versionLocate the version file in the ePO installation directory, typically found in the core\VERSION.TXT or similar version file, or access the ePO web console and check the 'About' pageAffected if Installed version is < 5.10.0 or equals 5.10.0, indicating the environment is vulnerable
-
Confirm ePO web interface is accessibleAttempt to access the ePO web console URL (typically https://server:8443 or port 443/8443) to verify the web component is runningAffected if The web interface is accessible and the version is in the affected range, the reflected XSS could be exploited
-
Check if administrator authentication is requiredVerify that the ePO console requires valid administrator credentials to access protected pages where the XSS could executeAffected if The web console is accessible without authentication OR authenticated administrators use the system, the vulnerability could be triggered through social engineering
If ePolicy Orchestrator is installed and the web interface version is 5.10.0 or earlier, the environment is affected by this reflected XSS vulnerability.
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 13 or later to remediate the vulnerability. Additionally, educate administrators about avoiding untrusted links to reduce social engineering risk.
ePolicy Orchestrator 5.10.0 Update 13 or later
- Confirm current ePolicy Orchestrator version by navigating to Menu > Settings > Server Settings > ePolicy Orchestrator Domain
- Download ePO 5.10.0 Update 13 or later from the McAfee Product Downloads portal (requires valid grant)
- Review McAfee ePO 5.10.0 Update 13 Release Notes for any prerequisites
- Create a full backup of the ePO database and current ePO server state
- Test the update in a non-production environment first
- Apply the update during a planned maintenance window following McAfee's upgrade documentation
- Verify the update was successful and the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0857 — 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-0857 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