dbcve.org
Clearpass Policy ManagerApplication · Arubanetworks

CVE-2022-23671

HIGH · 7.5 CVSS v3.1 Published 2022-05-17
Fix available
A fix is available. Upgrade to 6.8.9 or later.
See remediation →
84/100
Remediation priority · High
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 authenticated information disclosure 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

An authenticated remote information disclosure vulnerability in Aruba ClearPass Policy Manager allows authenticated users to access sensitive information they are not authorized to view. The vulnerability is exploitable over the network and affects multiple versions up to the thresholds specified.

MitigationApply the vendor-released updates for ClearPass Policy Manager: upgrade to version 6.10.5 or later, 6.9.10 or later, or 6.8.9-HF3 or later, depending on the current installed version 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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. Confirm Aruba ClearPass Policy Manager is installed
    Identify whether Aruba ClearPass Policy Manager is deployed in your environment. Check asset inventory, running services on relevant hosts, or consult with infrastructure administrators.
    Affected if The product is Aruba ClearPass Policy Manager and matches the affected version range.
  2. Determine the installed version of ClearPass Policy Manager
    Access the ClearPass CLI or web administration interface and locate the version information. In the CLI, this is typically shown at login or via a version command. In the web UI, it is usually displayed in the About or System Information section.
    Affected if The installed version falls within these ranges: <= 6.7.14; >= 6.8.0 and < 6.8.9; >= 6.9.0 and <= 6.9.9; >= 6.10.0 and <= 6.10.4; or exactly version 6.8.9.
  3. Verify that user authentication is configured and accessible
    Check if ClearPass has local or external user accounts configured and that the web-based policy manager interface or API is network-accessible. Confirm that user authentication mechanisms are enabled.
    Affected if Authentication is enabled and users can log in to ClearPass Policy Manager, making the unauthorized information disclosure possible.

You are affected if Aruba ClearPass Policy Manager is running a version within the affected ranges listed and user authentication is configured.

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 the vendor-released updates for ClearPass Policy Manager: upgrade to version 6.10.5 or later, 6.9.10 or later, or 6.8.9-HF3 or later, depending on the current installed version branch.

Recommended fix Moderate confidence

Upgrade to ClearPass Policy Manager 6.10.5 or later (6.9.10+, 6.8.10+, or 6.7.15+ as appropriate for your release branch)

  1. 1. Backup the current ClearPass Policy Manager configuration before initiating the upgrade
  2. 2. Download the appropriate ClearPass Policy Manager upgrade image from the Aruba support portal (www.arubanetworks.com)
  3. 3. Access the ClearPass Policy Manager administration interface
  4. 4. Navigate to Administration > Server Manager > Server Management
  5. 5. Select the node to upgrade and click on the upgrade option
  6. 6. Upload the downloaded upgrade image and initiate the upgrade process
  7. 7. Monitor the upgrade progress and ensure the system reboots successfully
  8. 8. After upgrade completion, verify the ClearPass Policy Manager version reflects the fixed release
Caveat Standard upgrade best practices apply - review Aruba upgrade guide for your version and ensure compatibility with integrated systems before proceeding

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
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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