CVE-2018-7067
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 Remote Authentication bypass in Aruba ClearPass Policy Manager leads to complete cluster compromise. An authentication flaw in all versions of ClearPass could allow an attacker to compromise the entire cluster through a specially crafted API call. Network access to the administrative web interface is required to exploit this vulnerability. Resolution: Fixed in 6.7.6 and 6.6.10-hotfix.
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 confidenceAuthentication bypass vulnerability in Aruba ClearPass Policy Manager allows remote attackers with network access to the administrative web interface to bypass authentication through specially crafted API calls, leading to complete cluster compromise.
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< 6.6.10>= 6.7.0, < 6.7.6CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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 ClearPass Policy Manager versionLog into the ClearPass administrative web interface and navigate to the About or System Information page to view the installed version number. Alternatively, access the CLI and run the command to display the firmware version (for example, 'show version' or 'show system information').Affected if The installed version falls within < 6.6.10 or >= 6.7.0 and < 6.7.6.
-
Confirm network accessibility of admin web interfaceDetermine if the ClearPass administrative web interface (typically ports 443 or 8080) is reachable from untrusted networks. Check firewall rules, ACLs, or VPN policies that govern access to the management IP address. Use a port scan or connectivity test from an external location to verify exposure.Affected if The admin web interface is accessible from networks that are not trusted or are outside the organization's security perimeter.
-
Check for API endpoint exposureVerify whether the ClearPass API endpoints (typically at /api/ or /oauth/paths) are accessible over the network. Review reverse proxy or load balancer configurations that may expose these paths, and confirm if the API service is enabled and listening on accessible interfaces.Affected if The API endpoints are reachable from untrusted networks without additional authentication barriers.
-
Review admin user accounts for unauthorized accessAudit the ClearPass admin user accounts through the web interface under Administration > Users > Administrators. Look for unfamiliar accounts, unexpected privilege escalations, or accounts created around the time of potential exploitation. Check audit logs for unusual API call patterns.Affected if Unexpected admin accounts exist or audit logs show anomalous API authentication events.
You are affected if your ClearPass Policy Manager version is below 6.6.10 or between 6.7.0 and 6.7.6, AND the administrative web interface or API endpoints are accessible from untrusted networks.
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 data6.6.106.7.6
Upgrade to version 6.7.6 or 6.6.10-hotfix. Additionally, restrict network access to the administrative web interface to trusted IPs as defense-in-depth.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7067 — 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-7067 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