dbcve.org
Clearpass Policy ManagerApplication · Arubanetworks

CVE-2022-23658

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 · high confidence

A remote authentication bypass vulnerability in Aruba ClearPass Policy Manager allows unauthenticated attackers to bypass the authentication mechanism and gain unauthorized access to the system. The vulnerability affects multiple version branches down to 6.7.x.

MitigationApply the vendor-released updates for ClearPass Policy Manager (upgrade to 6.10.5, 6.9.10, 6.8.9-HF3, or later versions) to remediate this critical authentication bypass.

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. Identify ClearPass Policy Manager version via web interface
    Log into the ClearPass Policy Manager admin web interface and navigate to Administration > About > Licensing to view the exact version number displayed.
    Affected if The displayed version falls within any of these ranges: < 6.8.9, = 6.8.9, >= 6.9.0 and < 6.9.10, or >= 6.10.0 and < 6.10.5.
  2. Identify ClearPass version via CLI
    SSH or console access to the ClearPass appliance and run the command: show version or cat /etc/version to retrieve the installed software version.
    Affected if The CLI-reported version matches any of the affected ranges listed above.
  3. Check ClearPass build or patch level
    In the web interface under Administration > About, look for build numbers or hotfix identifiers (such as HF1, HF2, HF3) that indicate whether a patch has been applied.
    Affected if The build shows no hotfix applied or the hotfix level is below HF3 for the 6.8.x branch.
  4. Verify authentication configuration exposure
    Review the ClearPass Policy Manager authentication profiles and network access settings under Configuration > Authentication to confirm whether the built-in authentication mechanisms are in active use.
    Affected if ClearPass native authentication is enabled and the version is within the affected ranges, exposing the bypass vulnerability.

A user is affected if their ClearPass Policy Manager version is 6.8.x before HF3, 6.9.x before 6.9.10, or 6.10.x before 6.10.5, with native authentication enabled.

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 vendor-released updates for ClearPass Policy Manager (upgrade to 6.10.5, 6.9.10, 6.8.9-HF3, or later versions) to remediate this critical authentication bypass.

Recommended fix High confidence

Upgrade to ClearPass Policy Manager 6.10.5 (or later 6.10.x), 6.9.10 (or later 6.9.x), or a version newer than 6.8.9 depending on your current branch

  1. Identify the current ClearPass Policy Manager version from the Administration > Server Manager > Server Configuration page
  2. Download the appropriate fixed version from Aruba's support portal based on your current branch (6.10.5+, 6.9.10+, or a version newer than 6.8.9)
  3. Backup the ClearPass configuration using the Backup & Restore feature in Administration > Backup & Restore
  4. Schedule a maintenance window as this upgrade may require service interruption
  5. Upload the upgrade file via the ClearPass web UI under Maintenance > System > Software Upgrade
  6. Follow the on-screen prompts to install the upgrade
  7. After upgrade, verify the version matches the expected fixed release
  8. Confirm normal authentication operations are functioning properly
Caveat Standard upgrade precautions apply - review release notes for any configuration changes or migration steps; test in non-production environment first

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
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
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,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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