CVE-2022-23667
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 confidenceAn authenticated remote command injection vulnerability exists in Aruba ClearPass Policy Manager. An attacker with valid credentials can inject and execute arbitrary commands on the underlying operating system due to insufficient input validation.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed ClearPass Policy Manager versionAccess the ClearPass administration interface and navigate to the About or System Information page, or use the CLI command 'show version' if you have shell accessAffected 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
-
Verify the specific patch level for version 6.8.9If the version shows 6.8.9 exactly, check whether Hotfix 3 (HF3) or higher has been appliedAffected if The version shows 6.8.9 without HF3 applied (i.e., not 6.8.9-HF3 or later)
-
Confirm the vulnerability requires authenticationNote that this flaw requires an attacker to have valid ClearPass credentials, review the account inventory and identify who has administrative or operator-level accessAffected if Valid user accounts exist in ClearPass, particularly administrative accounts that could be leveraged for this injection
Your environment is affected if the installed ClearPass Policy Manager version is less than 6.8.9-HF3, or falls between 6.9.0-6.9.9, or falls between 6.10.0-6.10.4.
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 the available software updates from Aruba that address this vulnerability, upgrading to versions newer than those affected (6.10.5+, 6.9.10+, 6.8.9-HF3+, or later).
Upgrade to ClearPass Policy Manager 6.8.9, 6.9.10, or 6.10.5 (or later) depending on your current branch
- 1. Identify the currently installed ClearPass Policy Manager version via the web UI (Dashboard > About) or CLI (show version)
- 2. Determine which upgrade path applies based on current version: if running 6.7.x or 6.8.x, upgrade to 6.8.9 or later; if running 6.9.x, upgrade to 6.9.10 or later; if running 6.10.x, upgrade to 6.10.5 or later
- 3. Download the appropriate upgrade ISO from the Aruba support portal (https://asp.arubanetworks.com) using valid support credentials
- 4. Backup the current ClearPass configuration via Administration > Backup & Restore > Backup Now
- 5. Upload the upgrade ISO via the ClearPass web UI: Administration > Software Updates > Upload Upgrade Package
- 6. Initiate the upgrade and monitor the process; the system will reboot automatically
- 7. After reboot, verify the new version is installed and confirm all services are operational
- 8. Validate that the configuration was preserved and test critical functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23667 — 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-23667 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