CVE-2022-23692
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 · uneditedVulnerabilities in the web-based management interface of ClearPass Policy Manager could allow an authenticated remote attacker to conduct SQL injection attacks against the ClearPass Policy Manager instance. An attacker could exploit these vulnerabilities to obtain and modify sensitive information in the underlying database potentially leading to complete compromise of the ClearPass Policy Manager cluster in Aruba ClearPass Policy Manager version(s): 6.10.x: 6.10.6 and below; 6.9.x: 6.9.11 and below. Aruba has released upgrades for Aruba ClearPass Policy Manager that address these security vulnerabilities.
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 confidenceSQL injection vulnerabilities exist in the web-based management interface of Aruba ClearPass Policy Manager. An authenticated remote attacker can inject malicious SQL queries through the interface to access, exfiltrate, or modify sensitive data in the underlying database. This could lead to full compromise of the ClearPass Policy Manager cluster.
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.9.0, < 6.9.12>= 6.10.0, < 6.10.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed ClearPass Policy Manager versionAccess the web-based management interface and navigate to Administration > About, or use CLI command 'show version' to retrieve the exact version numberAffected if Version is 6.9.0 through 6.9.11, or 6.10.0 through 6.10.6 (falls within >=6.9.0,<6.9.12 or >=6.10.0,<6.10.7)
-
Confirm web management interface is enabledVerify the ClearPass Policy Manager web-based management interface is accessible and operational by attempting to reach the login page at the configured management IP/hostnameAffected if Web interface is accessible and responding (this is the attack vector for the SQL injection)
-
Identify authentication method for web interfaceReview the authentication configuration in ClearPass to determine if local database authentication or external authentication (like Active Directory, LDAP, RADIUS) is in use for admin accountsAffected if Local database authentication is used for admin accounts, as the attacker would need valid credentials to authenticate before exploiting the SQL injection
Your environment is affected if ClearPass Policy Manager version is 6.9.0-6.9.11 or 6.10.0-6.10.6 and the web-based management interface is accessible, since an authenticated attacker could inject SQL queries through that interface.
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.9.126.10.7
Upgrade Aruba ClearPass Policy Manager to version 6.10.7 or higher (for 6.10.x branches) or 6.9.12 or higher (for 6.9.x branches) as released by Aruba. Apply the patches in accordance with Aruba's upgrade procedures.
6.9.12 or later for 6.9.x branch; 6.10.7 or later for 6.10.x branch
- 1. Back up the ClearPass Policy Manager configuration and database before starting the upgrade process
- 2. Download the appropriate fixed version from the Aruba support portal (6.9.12 or later for 6.9.x users, 6.10.7 or later for 6.10.x users)
- 3. Review Aruba's upgrade documentation for ClearPass Policy Manager to ensure prerequisites are met
- 4. Execute the upgrade following Aruba's standard upgrade procedure for ClearPass Policy Manager
- 5. After upgrade completes, verify the ClearPass Policy Manager services are running correctly
- 6. Log in to the web-based management interface and confirm the version reflects the patched release
- 7. Test critical functionality to ensure the upgrade did not introduce issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation8.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23692 — 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-23692 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