Epolicy OrchestratorApplication · Mcafee

CVE-2021-23890

MEDIUM · 6.5 CVSS v3.1 Published 2021-03-26
Fix available
A fix is available. Upgrade to 5.9.1 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Information leak vulnerability in the Agent Handler of McAfee ePolicy Orchestrator (ePO) prior to 5.10 Update 10 allows an unauthenticated user to download McAfee product packages (specifically McAfee Agent) available in ePO repository and install them on their own machines to have it managed and then in turn get policy details from the ePO server. This can only happen when the ePO Agent Handler is installed in a Demilitarized Zone (DMZ) to service machines not connected to the network through a VPN.

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 confidence

An unauthenticated attacker can download McAfee Agent packages from an ePO Agent Handler deployed in a DMZ, install the agent on their own system, and register it with the ePO server to receive policy details. This only affects DMZ deployments serving machines without VPN connectivity.

MitigationUpdate McAfee ePO to version 5.10 Update 10 or later. Additionally, restrict access to the DMZ-hosted Agent Handler to only legitimate managed endpoints and implement network segmentation to prevent unauthorized registration.

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
Epolicy OrchestratorApplication
Affected:< 5.9.1= 5.10.0

CVSS 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
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify ePO version
    Check the installed McAfee ePolicy Orchestrator version through the ePO console (typically in the Dashboard or About section) or via installed programs list
    Affected if Version is lower than 5.9.1 or exactly 5.10.0
  2. Confirm Agent Handler DMZ deployment
    Review network architecture documentation or verify if an Agent Handler system is deployed in a DMZ (demilitarized zone) network segment outside the internal firewall
    Affected if An Agent Handler is deployed in a DMZ network segment
  3. Verify target machines lack VPN connectivity
    Determine whether the DMZ-hosted Agent Handler is serving endpoints that do not use VPN to connect to the internal network (e.g., remote employees, branch offices without VPN)
    Affected if The Agent Handler serves machines without VPN connectivity to the internal ePO server
  4. Check agent package download access controls
    Inspect the Agent Handler configuration to determine if unauthenticated (anonymous) download of agent installation packages is permitted
    Affected if Agent packages can be downloaded without authentication
  5. Check agent registration restrictions
    Inspect ePO server settings to verify whether new agent registrations from unknown systems are allowed without authentication or approval
    Affected if Unauthenticated agent registration to the ePO server is permitted

The environment is affected if ePO version is below 5.9.1 or exactly 5.10.0, AND an Agent Handler is deployed in a DMZ serving machines without VPN connectivity, AND unauthenticated agent package download and registration are enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 5.9.1 or later
Fixed in 5.9.1
Interim mitigation

Update McAfee ePO to version 5.10 Update 10 or later. Additionally, restrict access to the DMZ-hosted Agent Handler to only legitimate managed endpoints and implement network segmentation to prevent unauthorized registration.

Fix this in Epolicy Orchestrator Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-23890 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-23890 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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