dbcve.org
Clearpass Policy ManagerApplication · Arubanetworks

CVE-2022-23669

HIGH · 8.8 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to 6.8.9 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 authorization 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 authorization bypass vulnerability in Aruba ClearPass Policy Manager allows unauthenticated or unauthorized remote attackers to bypass authorization controls, potentially gaining unauthorized access to the network access control system and its management functions.

MitigationApply vendor-released updates: upgrade to ClearPass Policy Manager versions 6.10.5, 6.9.10, 6.8.9-HF3, or 6.7.x and above depending on your current branch.

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.7.14>= 6.8.0, < 6.8.9>= 6.9.0, <= 6.9.9>= 6.10.0, <= 6.10.4= 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 checks

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

  1. Check ClearPass Policy Manager version via CLI
    SSH to the ClearPass server and run the command 'show version' or 'show appliance details' to retrieve the installed software version.
    Affected if The displayed version falls within any of these ranges: <= 6.7.14, >= 6.8.0 and < 6.8.9, 6.8.9, >= 6.9.0 and <= 6.9.9, or >= 6.10.0 and <= 6.10.4.
  2. Check ClearPass Policy Manager version via web interface
    Log into the ClearPass web UI (typically https://<hostname>/) and navigate to Administration > About or the System > Diagnostics > About page to view the installed version.
    Affected if The version shown is within the affected ranges listed in step 1.
  3. Verify the exact version number
    Confirm the full version string including any build numbers or patch levels (for example, distinguish between 6.8.9 and 6.8.9-HF3).
    Affected if The version is exactly 6.8.9 (not 6.8.9-HF3 or higher) or is any version <= 6.7.14, between 6.8.0-6.8.8, between 6.9.0-6.9.9, or between 6.10.0-6.10.4.

You are affected if your installed ClearPass Policy Manager version is any version other than 6.7.15 or higher, 6.8.9-HF3 or higher, 6.9.10 or higher, or 6.10.5 or higher.

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 or later
Fixed in 6.8.9
Interim mitigation

Apply vendor-released updates: upgrade to ClearPass Policy Manager versions 6.10.5, 6.9.10, 6.8.9-HF3, or 6.7.x and above depending on your current branch.

Recommended fix High confidence

Upgrade to the latest patch release for your version branch: 6.7.15+, 6.8.10+, 6.9.10+, or 6.10.5+

  1. Identify your current ClearPass Policy Manager version from the Administration > About page
  2. Determine which version branch you are running (6.7.x, 6.8.x, 6.9.x, or 6.10.x)
  3. For version 6.7.x: Upgrade to version 6.7.15 or later
  4. For version 6.8.x: Upgrade to version 6.8.10 or later
  5. For version 6.9.x: Upgrade to version 6.9.10 or later
  6. For version 6.10.x: Upgrade to version 6.10.5 or later
  7. Download the appropriate upgrade from the Aruba Support Portal (https://asp.arubanetworks.com)
  8. Back up your ClearPass configuration before performing the upgrade
Caveat Point releases typically have minimal breaking changes; review Aruba release notes for any known issues before upgrading

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
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,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 $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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