dbcve.org
Clearpass Policy ManagerApplication · Arubanetworks

CVE-2018-7066

CRITICAL · 9.0 CVSS v3.0 Published 2018-12-07
Fix available
A fix is available. Upgrade to 6.6.10 / 6.7.5 or later.
See remediation →
99/100
Remediation priority · Urgent
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
An unauthenticated remote command execution exists in Aruba ClearPass Policy Manager on linked devices. The ClearPass OnConnect feature permits administrators to link other network devices into ClearPass for the purpose of collecting enhanced information about connected endpoints. A defect in the API could allow a remote attacker to execute arbitrary commands on one of the linked devices. This vulnerability is only applicable if credentials for devices have been supplied to ClearPass under Configuration -> Network -> Devices -> CLI Settings. Resolution: Fixed in 6.7.5 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 confidence

Aruba ClearPass Policy Manager contains an unauthenticated remote command execution vulnerability in the OnConnect feature API. This feature allows administrators to link network devices for enhanced endpoint information collection. A defect in the API permits remote attackers to execute arbitrary commands on linked devices without authentication.

MitigationUpgrade ClearPass Policy Manager to version 6.7.5 or 6.6.10-hotfix. Additionally, review and restrict CLI credentials configured under Configuration -> Network -> Devices -> CLI Settings to minimize exposure if patching is delayed.

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
Clearpass Policy ManagerApplication
Affected:< 6.6.10>= 6.7.0, < 6.7.5

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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/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 checks

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

  1. Determine installed ClearPass Policy Manager version
    Access the ClearPass admin UI and navigate to Administration > About, or use the CLI command 'show version' to retrieve the exact version number
    Affected if The version is less than 6.6.10, or is 6.7.0 through 6.7.4 (within the affected ranges)
  2. Verify OnConnect feature status
    Navigate to Configuration > Network > Devices in the ClearPass admin interface and locate the OnConnect or endpoint profiling settings to determine if this feature is configured
    Affected if OnConnect feature is enabled or configured on the system
  3. Check for linked network devices
    Review the device list under Configuration > Network > Devices to identify any network devices that have been added for endpoint information collection via OnConnect
    Affected if Any network devices are configured in the OnConnect feature
  4. Inspect OnConnect API accessibility
    Attempt to access the OnConnect API endpoint (typically /api/onc/) from an unauthenticated perspective or review API access logs to determine if the endpoint responds without credentials
    Affected if The OnConnect API responds to unauthenticated requests

You are affected if your ClearPass version falls within < 6.6.10 or >= 6.7.0 AND < 6.7.5, AND the OnConnect feature is enabled with configured network devices.

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.

dbcve · scoped
Upgrade available Upgrade to 6.6.10 / 6.7.5 or later
Fixed in 6.6.106.7.5
Interim mitigation

Upgrade ClearPass Policy Manager to version 6.7.5 or 6.6.10-hotfix. Additionally, review and restrict CLI credentials configured under Configuration -> Network -> Devices -> CLI Settings to minimize exposure if patching is delayed.

Recommended fix High confidence

Upgrade to Clearpass Policy Manager 6.7.5 or apply 6.6.10-hotfix

  1. 1. Identify the current Clearpass Policy Manager version by navigating to Administration > About ClearPass in the web interface
  2. 2. Download the appropriate fixed version: upgrade to 6.7.5 if running 6.7.x, or apply 6.6.10-hotfix if running 6.6.x
  3. 3. Backup the current ClearPass configuration before performing the upgrade
  4. 4. Ensure no devices are configured with CLI credentials under Configuration > Network > Devices > CLI Settings if possible, as this is the attack vector
  5. 5. Apply the upgrade following Aruba's standard upgrade procedures documented in the ClearPass Deployment Guide
  6. 6. Verify the upgrade was successful and the version reflects the fixed release
  7. 7. After upgrade, review CLI Settings configuration and remove any unnecessary device credentials
Caveat Standard upgrade precautions apply - backup configuration, ensure compatibility with integration systems, and plan maintenance window

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Clearpass Policy Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7066 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2018-7066 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