CVE-2022-0862
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 lack of password change protection vulnerability in a depreciated API of McAfee Enterprise ePolicy Orchestrator (ePO) prior to 5.10 Update 13 allows a remote attacker to change the password of a compromised session without knowing the existing user's password. This functionality was removed from the User Interface in ePO 10 and the API has now been disabled. Other protection is in place to reduce the likelihood of this being successful through sending a link to a logged in user.
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 deprecated API in McAfee Enterprise ePolicy Orchestrator (ePO) prior to version 5.10 Update 13 lacks proper password change protection, allowing a remote attacker to change a user's password without knowledge of the current password. The vulnerable API was removed from the UI in ePO 10 but remained functional in the backend until being disabled in the patch.
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
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 versionLocate the ePO server and check the installed version number - typically visible in the ePO console header or in the installation directory version fileAffected if The version is 5.10.0 or any version prior to 5.10.0 (e.g., 5.9.x, 5.8.x, etc.)
-
Confirm Update 13 patch levelIf running ePO 5.10.x, verify whether Update 13 has been applied by checking the ePO console for the full version string or the patch installation statusAffected if Running 5.10.0 through 5.10.12 without Update 13 applied (the Update 13 patch disables the vulnerable deprecated API)
-
Check for ePO 10.x installationsIf ePO version is 10.x or higher, verify the patch level - note that the UI removed this API in ePO 10 but the backend remained vulnerable until Update 13Affected if Running ePO 10.x, 11.x, or higher without the corresponding Update 13 fix applied to disable the deprecated backend API
You are affected if your ePO version is 5.10.0 or earlier, or if you are on 5.10.x through 5.10.12, or on ePO 10.x+ without the Update 13 equivalent patch applied.
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 to ePO 5.10 Update 13 or later, which disables the deprecated API. This is the only remediation as the vulnerable functionality has been removed.
5.10.0 with Update 13 (or later)
- Upgrade McAfee Enterprise ePolicy Orchestrator to version 5.10.0 with Update 13 applied
- After upgrading, verify the deprecated API has been disabled by checking the ePO console for any remaining references to the old password change API
- As an additional precaution, restrict network access to the ePO server to trusted administrative networks only
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.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 $5,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0862 — 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-0862 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