dbcve.org
Clearpass Policy ManagerApplication · Arubanetworks

CVE-2022-23660

CRITICAL · 10.0 CVSS v3.1 Published 2022-05-16
Fix available
A fix is available. Upgrade to 6.8.9 / 6.9.10 or later.
See remediation →
100/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
A remote authentication bypass vulnerability was discovered in Aruba ClearPass Policy Manager version(s): 6.10.4 and below, 6.9.9 and below, 6.8.9-HF2 and below, 6.7.x and below. Aruba has released updates to ClearPass Policy Manager that address this security vulnerability.

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 confidence

A remote authentication bypass vulnerability in Aruba ClearPass Policy Manager allows remote attackers to circumvent authentication mechanisms and gain unauthorized access to the policy management system without valid credentials.

MitigationApply the available security updates from Aruba for all affected versions (6.10.x, 6.9.x, 6.8.x, 6.7.x) as specified in the official Aruba security advisory.

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.8.9>= 6.9.0, < 6.9.10>= 6.10.0, < 6.10.5= 6.8.9

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

CVSS:3.1/AV:N/AC:L/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. Check installed ClearPass Policy Manager version
    Access the ClearPass web UI and navigate to Administration > About, or use the CLI command `show version` to display the current firmware version
    Affected if The displayed version is < 6.8.9, or >= 6.9.0 and < 6.9.10, or >= 6.10.0 and < 6.10.5 (including version 6.8.9 itself)
  2. Confirm the ClearPass Policy Manager is externally accessible
    Verify if the ClearPass management interface (HTTPS port 443 or configured admin port) is reachable from untrusted networks or the internet
    Affected if The admin interface is exposed to untrusted networks and the version falls within the affected ranges
  3. Review authentication configuration
    Check the authentication methods configured in ClearPass under Administration > Authentication > Methods to confirm the default authentication mechanisms are in use
    Affected if Default authentication methods are enabled and the version is vulnerable
  4. Check for unauthorized access indicators
    Review ClearPass audit logs under Monitoring > Logs > Audit for any successful logins from unfamiliar IP addresses or outside expected administrative windows
    Affected if Unexpected administrative access is observed and the version is within the affected ranges

If the installed ClearPass Policy Manager version is 6.8.x before 6.8.9, 6.9.x before 6.9.10, or 6.10.x before 6.10.5, and the management interface is accessible, the environment is likely affected by this authentication bypass vulnerability.

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.8.9 / 6.9.10 / 6.10.5 or later
Fixed in 6.8.96.9.106.10.5
Interim mitigation

Apply the available security updates from Aruba for all affected versions (6.10.x, 6.9.x, 6.8.x, 6.7.x) as specified in the official Aruba security advisory.

Recommended fix High confidence

6.8.9 or higher for 6.8.x branches; 6.9.10 or higher for 6.9.x branches; 6.10.5 or higher for 6.10.x branches

  1. 1. Identify the currently installed ClearPass Policy Manager version via the WebUI (Dashboard > About) or CLI (show version)
  2. 2. Determine the appropriate upgrade path based on current version: if on 6.7.x, upgrade to 6.8.9 or later; if on 6.8.x, upgrade to 6.8.9 or later; if on 6.9.x, upgrade to 6.9.10 or later; if on 6.10.x, upgrade to 6.10.5 or later
  3. 3. Download the appropriate upgrade image from the Aruba Airheads or Aruba Support Portal at https://asp.arubanetworks.com/
  4. 4. Backup the ClearPass configuration via the WebUI (Administration > Backup & Restore) or CLI (backup) before upgrading
  5. 5. Apply the upgrade via the WebUI (Administration > Software Update) or CLI (upgrade <image>), allowing sufficient time for the process to complete
  6. 6. Verify the upgrade was successful by checking the version number post-reboot
  7. 7. Validate that ClearPass services are running normally and policy enforcement is functioning
Caveat Standard upgrade downtime applies; ensure backup is available; test in non-production environment before production deployment

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

Fix this in Clearpass Policy Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,180
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23660 — 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-2022-23660 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