CVE-2022-23696
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 in the web-based management interface of Aruba ClearPass Policy Manager allow authenticated remote attackers to inject malicious SQL queries, potentially enabling extraction and modification of sensitive database information and complete compromise of the ClearPass 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.
-
Identify the installed ClearPass Policy Manager versionLog into the ClearPass CLI or access the web UI and navigate to Administration > Server Manager > Server Information, or run 'show version' command via CLIAffected if The installed version falls within 6.9.0 through 6.9.11, or 6.10.0 through 6.10.6 (the version shown is less than 6.9.12 or 6.10.7)
-
Confirm the web-based management interface is enabledCheck via CLI with 'show web-server' or access the web UI at the management IPAffected if The web-based management interface is accessible and enabled on standard HTTPS ports (443/8443)
-
Verify authentication is configured for the management interfaceNavigate to Administration > Access Management > Administrative Users in the web UI, or check 'show admin-user' via CLIAffected if Local or external authentication (RADIUS/LDAP) is configured, meaning an attacker with valid credentials could exploit the SQL injection
You are affected if your 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 with valid administrative 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.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), or to the latest available version as recommended by Aruba.
Upgrade to ClearPass Policy Manager 6.9.12 or 6.10.7 (or later) depending on your current major version branch
- Back up the current ClearPass Policy Manager configuration and export critical data
- Review the Aruba ClearPass upgrade guide for your current version at support.arubanetworks.com
- Download ClearPass Policy Manager version 6.9.12 (if on 6.9.x) or 6.10.7 (if on 6.10.x) from the Aruba support portal
- Schedule a maintenance window as upgrades require downtime
- Apply the upgrade following Aruba's documented upgrade procedure (typically via the WebUI or CLI)
- After upgrade completes, verify the new version is running: 6.9.12 or 6.10.7
- Confirm the SQL injection vulnerability is resolved by checking the system is not exposing database errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23696 — 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-23696 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