CVE-2018-6672
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 · uneditedInformation disclosure vulnerability in McAfee ePolicy Orchestrator (ePO) 5.3.0 through 5.3.3 and 5.9.0 through 5.9.1 allows authenticated users to view sensitive information in plain text format via unspecified vectors.
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 confidenceAuthenticated users of McAfee ePolicy Orchestrator versions 5.3.0-5.3.3 and 5.9.0-5.9.1 can view sensitive information in plain text due to an information disclosure vulnerability. The exact attack vector is not specified in the advisory, but the requirement for authentication suggests this is an internal threat or compromised credential scenario.
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.3.0, <= 5.3.3>= 5.9.0, <= 5.9.1CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Locate McAfee ePolicy Orchestrator installationCheck the default installation path C:\Program Files\McAfee\ePolicy Orchestrator or look for the ePO directory on the systemAffected if ePO is installed on the system
-
Identify ePO version numberOpen the file ePO_install_dir\server\conf\version.properties or check the Windows registry key HKLM\SOFTWARE\McAfee\ePolicy Orchestrator\CurrentVersion for the value 'CurrentVersion'Affected if The version cannot be determined or the file/registry key does not exist
-
Compare installed version against affected rangesMatch the identified version against 5.3.0 through 5.3.3, or 5.9.0 through 5.9.1Affected if The installed version falls within 5.3.0-5.3.3 or 5.9.0-5.9.1
-
Check for existing ePO user accountsLog into the ePO console and navigate to User Management or review the database table dbo.EPOUsers to see if any user accounts are definedAffected if There are authenticated user accounts configured in ePO
The environment is affected if McAfee ePO is installed with a version in the range 5.3.0-5.3.3 or 5.9.0-5.9.1 and there are user accounts present that could potentially access the sensitive information.
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.
From vendor dataApply the vendor patch from McAfee to address this vulnerability in affected ePO versions. Ensure least-privilege access controls are enforced for ePO user accounts to limit exposure.
- Consultation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-6672 — 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-2018-6672 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