CVE-2018-7058
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, all versions of 6.6.x prior to 6.6.9 are affected by an authentication bypass vulnerability, an attacker can leverage this vulnerability to gain administrator privileges on the system. The vulnerability is exposed only on ClearPass web interfaces, including administrative, guest captive portal, and API. Customers who do not expose ClearPass web interfaces to untrusted users are impacted to a lesser extent.
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 versions 6.6.x prior to 6.6.9 contain an authentication bypass vulnerability in the web interfaces (administrative, guest captive portal, and API). This allows unauthenticated or authenticated attackers to gain administrator privileges on the system.
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.0, < 6.6.9CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 ClearPass versionAccess the ClearPass administrator UI or check the system via CLI using 'show version' or similar command to retrieve the installed software version.Affected if The installed version is 6.6.0 through 6.6.8 (any version >= 6.6.0 but < 6.6.9).
-
Verify web interface accessibilityConfirm that the ClearPass web interfaces (administrative UI, guest captive portal, or API endpoints) are reachable on the network.Affected if Any of these web interfaces are accessible from a network where untrusted users could potentially connect.
-
Check authentication configurationReview the web interface authentication settings in ClearPass Admin UI under Configuration > Authentication or examine the API service configuration.Affected if Web authentication is configured but the version is vulnerable, meaning the authentication bypass could be exploited.
You are affected if ClearPass Policy Manager version is 6.6.0 through 6.6.8 and any web interface (administrative, guest captive portal, or API) is exposed.
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 · scoped6.6.9
Upgrade to ClearPass version 6.6.9 or later. If immediate upgrade is not possible, restrict access to ClearPass web interfaces from untrusted networks to reduce exposure.
ClearPass Policy Manager 6.6.9 or later
- 1. Create a full backup of the ClearPass Policy Manager configuration using the administrative UI or CLI
- 2. Download the fixed version (6.6.9 or later) from the Aruba support portal at arubanetworks.com
- 3. Access the ClearPass administrative interface and navigate to the Software Upgrade section
- 4. Upload and apply the 6.6.9 (or later) software upgrade following Aruba's documented upgrade procedures
- 5. Verify the upgrade completed successfully by checking the system health and version information
- 6. Confirm the web interfaces (administrative, guest captive portal, and API) are functioning correctly after the upgrade
- 7. Validate that administrator access controls are working as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7058 — 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-7058 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