dbcve.org
Clearpass Policy ManagerApplication · Arubanetworks

CVE-2022-23673

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

Authenticated remote command injection vulnerability in Aruba ClearPass Policy Manager allows attackers with valid credentials to execute arbitrary commands on the underlying system. The vulnerability affects versions 6.10.4 and below, 6.9.9 and below, 6.8.9-HF2 and below, and 6.7.x and below.

MitigationApply vendor-supplied updates to ClearPass Policy Manager to address this vulnerability. Organizations should prioritize patching given the CVSS 7.2 HIGH severity and authenticated attack vector.

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

CVSS:3.1/AV:N/AC:L/PR:H/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. Determine ClearPass Policy Manager version
    Log into the ClearPass CLI as admin and run 'show version' or access the web UI and navigate to Administration > Server Manager > Server Information to view the version number
    Affected if The displayed version falls within <= 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. Confirm management interface is accessible
    Verify that the ClearPass Policy Manager web interface (HTTPS on port 443 or 4433) is reachable from network locations where untrusted users could operate
    Affected if The web management interface is exposed to network segments beyond trusted administrators
  3. Review administrator account access
    Check for the existence of user accounts with administrative privileges in ClearPass by navigating to Configuration > Identity > Users or using 'show user' CLI command
    Affected if Any administrator-level accounts exist in the system, as the vulnerability requires valid credentials to exploit

Your environment is affected if the installed ClearPass Policy Manager version is within the affected ranges AND the management interface is accessible to potential attackers who could obtain or already have valid admin credentials.

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-supplied updates to ClearPass Policy Manager to address this vulnerability. Organizations should prioritize patching given the CVSS 7.2 HIGH severity and authenticated attack vector.

Recommended fix High confidence

ClearPass Policy Manager 6.10.5 (or latest 6.10.x), 6.9.10 (or latest 6.9.x), 6.8.10 (or latest 6.8.x), or 6.7.15 (or latest 6.7.x)

  1. 1. Identify the current installed version of ClearPass Policy Manager
  2. 2. Determine which version branch you are currently running (6.7.x, 6.8.x, 6.9.x, or 6.10.x)
  3. 3. Download the appropriate fixed version from Aruba's support portal: for 6.10.x branch use 6.10.5 or later, for 6.9.x branch use 6.9.10 or later, for 6.8.x branch use 6.8.10 or later, for 6.7.x branch use 6.7.15 or later
  4. 4. Review Aruba upgrade documentation and release notes for your version branch
  5. 5. Schedule a maintenance window and perform a full backup of the ClearPass configuration
  6. 6. Follow Aruba's standard upgrade procedure for ClearPass Policy Manager
  7. 7. After upgrade, verify the new version is installed and confirm all services are running properly
  8. 8. Validate that the vulnerability is resolved by checking the ClearPass version and reviewing the security release notes
Caveat Standard ClearPass minor version upgrades typically preserve configuration; review release notes for any migration requirements or deprecated features specific to your version branch

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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