CVE-2022-23664
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 · uneditedA 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 confidenceAuthenticated remote command injection vulnerability in Aruba ClearPass Policy Manager allowing an authenticated attacker to execute arbitrary commands on the underlying system. Affects versions 6.10.4 and below, 6.9.9 and below, 6.8.9-HF2 and below, and 6.7.x and below. CVSS 9.1 indicates network-exploitable, low-complexity attacks requiring only valid credentials.
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< 6.8.9>= 6.9.0, < 6.9.10>= 6.10.0, < 6.10.5= 6.8.9CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine ClearPass Policy Manager versionLog into the ClearPass CLI and run 'show version' or access the web UI and navigate to Administration > Server Manager > Server Configuration to view the version information.Affected if The installed version falls within any of these ranges: < 6.8.9, = 6.8.9, >= 6.9.0 through 6.9.9, >= 6.10.0 through 6.10.4, or 6.7.x and below, including 6.8.9-HF2 and below.
-
Identify management interface exposureReview network configuration to determine if the ClearPass management interface (HTTPS port 443/4433) is accessible from untrusted networks. Check firewall rules, ACLs, or VPN policies governing access to the ClearPass appliance.Affected if The management interface is reachable from outside trusted management networks or the internet.
-
Verify authentication endpoint accessibilityConfirm that the ClearPass login page is accessible. Try accessing https://<clearpass-ip>/tips/tipsLogin.action or the main management URL from the perspective of a potential attacker.Affected if The authentication endpoints are exposed without IP restriction, as this vulnerability requires valid credentials to exploit.
-
Check for operator account compromiseReview operator accounts in ClearPass: navigate to Administration > User Management > Operators in the web UI, or use 'show operator' in CLI. Look for any unauthorized or unexpected accounts.Affected if An attacker with valid operator credentials could exploit this command injection flaw.
A user is affected if their ClearPass Policy Manager version is 6.10.4 or below, 6.9.9 or below, 6.8.9 or below (including HF2), or any 6.7.x version, and the management interface is accessible to an attacker who could obtain or use valid credentials.
Generated from the published advisory. Verify against your own configuration.
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 · scoped6.8.96.9.106.10.5
Apply vendor-released updates for ClearPass Policy Manager per version-specific guidance. Restrict management interface access to trusted IPs if immediate patching is not feasible.
Upgrade to ClearPass Policy Manager 6.10.5 (or 6.9.10 for 6.9.x, or 6.8.9-HF2 for 6.8.x)
- Identify your current ClearPass Policy Manager version from the WebUI or CLI
- Download the appropriate fixed version from Aruba's support portal: upgrade to 6.10.5 or later for 6.10.x, 6.9.10 or later for 6.9.x, or 6.8.9-HF2 or later for 6.8.x
- Review Aruba upgrade prerequisites and backup procedures in the official migration guide
- Perform a full backup of the ClearPass configuration before upgrading
- Upload the upgrade file via the ClearPass WebUI (Administration > Software Updates > Upload) or CLI
- Initiate the upgrade from the WebUI (Administration > Software Updates > Upgrade) or CLI using 'upgrade <image>','Allow sufficient time for the upgrade process to complete (do not interrupt power)
- Verify the upgrade was successful and the new version is running
- Confirm all services are operational and test critical functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2022-23664 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-23664 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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