CVE-2018-7079
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 · uneditedAruba ClearPass Policy Manager guest authorization failure. Certain administrative operations in ClearPass Guest do not properly enforce authorization rules, which allows any authenticated administrative user to execute those operations regardless of privilege level. This could allow low-privilege users to view, modify, or delete guest users. 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 confidenceAruba ClearPass Policy Manager has an authorization bypass vulnerability in ClearPass Guest where certain administrative operations fail to properly enforce privilege-level checks. Any authenticated administrative user, including those with low privileges, can view, modify, or delete guest user accounts that should be restricted to higher-privilege roles.
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 installationLocate the ClearPass server and confirm it is running. Check if the ClearPass Guest module is accessible via the web UI at /guest or via the administrative interface.Affected if ClearPass Policy Manager with ClearPass Guest module is deployed in the environment.
-
Determine installed ClearPass versionLog into the ClearPass CLI and run 'show version' or access Administration > Server Information in the web UI to retrieve the exact version number.Affected if The installed version is any release prior to 6.6.10, or any 6.7.x release prior to 6.7.6.
-
Verify ClearPass Guest configurationAccess the ClearPass web UI and navigate to Configuration > Guest Management to confirm guest accounts are being managed through ClearPass Guest.Affected if ClearPass Guest is actively configured and used to create or manage guest user accounts.
-
Review administrative user rolesIn the ClearPass web UI, go to Administration > User Management > Roles to enumerate existing administrative roles and identify any low-privilege admin accounts.Affected if There are administrative users assigned to roles with limited privileges who should not have access to guest account modifications.
-
Test authorization boundary for guest operationsUsing a low-privilege administrative account, attempt to view, modify, or delete guest user accounts through the ClearPass Guest interface to confirm if privilege enforcement is working.Affected if A low-privilege admin user can successfully view, modify, or delete guest accounts that should be restricted to higher-privilege roles.
The environment is affected if ClearPass Policy Manager is running a version below 6.6.10 or between 6.7.0 and 6.7.5, ClearPass Guest is configured, and low-privilege admin users can perform guest account operations that should require higher privileges.
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 ClearPass version 6.7.6 or apply the 6.6.10-hotfix. Until then, restrict administrative access to trusted high-privilege users only and audit logs for unauthorized guest user modifications.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7079 — 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-7079 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