CVE-2022-0859
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 · uneditedMcAfee Enterprise ePolicy Orchestrator (ePO) prior to 5.10 Update 13 allows a local attacker to point an ePO server to an arbitrary SQL server during the restoration of the ePO server. To achieve this the attacker would have to be logged onto the server hosting the ePO server (restricted to administrators) and to know the SQL server password.
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 confidenceMcAfee ePolicy Orchestrator prior to version 5.10 Update 13 contains a vulnerability where a local attacker with administrator-level access to the ePO server and knowledge of SQL credentials can redirect the ePO server to connect to an arbitrary SQL server during the restoration process, potentially enabling data manipulation or credential harvesting.
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
- Local
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
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 installed ePO versionLocate the ePolicy Orchestrator version information in the ePO console under 'Server Settings' > 'Repository' or check the installed software version on the ePO server itselfAffected if The installed version is any release prior to 5.10.0, or is exactly version 5.10.0 (versions 5.10.0 through 5.10.12 are all vulnerable)
-
Confirm restoration feature is accessibleVerify whether the ePO database restoration functionality is accessible on the ePO server, typically via the ePO console or command-line restore utilitiesAffected if The restoration feature is available and can be initiated by an administrator on the ePO server
-
Verify administrator access controlsReview the list of accounts granted administrator-level privileges on the ePO server through the ePO console user managementAffected if There are multiple administrator accounts or shared credentials in use, increasing the likelihood of a local attacker obtaining admin-level access
-
Check SQL credential storageInspect how SQL Server credentials are stored and accessed by the ePO server, looking for configuration files or credential stores that may be readable by administratorsAffected if SQL credentials are stored in a manner accessible to ePO administrators (as the attacker needs these credentials)
A user is affected if their ePO installation is version 5.10.0 or any earlier version, AND an administrator-level account can access the restoration functionality with knowledge of SQL credentials.
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
Apply ePO 5.10 Update 13 or later to remediate this vulnerability. Additionally, restrict administrator access to the ePO server and ensure SQL server passwords are stored securely.
ePolicy Orchestrator 5.10 Update 13 or later
- Review McAfee ePolicy Orchestrator upgrade documentation at kc.mcafee.com for version 5.10 Update 13
- Ensure you have a complete backup of the ePO database and configuration
- Verify that you have administrator access to the ePO server
- Download ePolicy Orchestrator 5.10 Update 13 or later from the McAfee download portal
- Stop all ePO services before beginning the upgrade
- Apply the upgrade following the standard ePO upgrade procedure
- Verify the upgrade was successful by checking the ePO console version information
- Confirm ePO services are running correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.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,392.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-0859 — 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-0859 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