CVE-2022-23694
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 ClearPass Policy Manager allow authenticated remote attackers to inject malicious SQL queries, potentially enabling database exfiltration, modification, and full cluster compromise.
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 ClearPass Policy Manager installationLocate the ClearPass Policy Manager server in your environment and confirm it is the Aruba product. Check inventory systems or network documentation for this device.Affected if ClearPass Policy Manager is not present in your environment.
-
Determine installed versionAccess the ClearPass admin UI or CLI and retrieve the current software version number. This is typically shown on the dashboard of the web management interface or via CLI command 'show version' or 'show system info'.Affected if The installed version falls within 6.9.0 to 6.9.11 inclusive, or 6.10.0 to 6.10.6 inclusive.
-
Verify web management interface is enabledConfirm the web-based management interface (HTTP/HTTPS on port 80/443 or 443/4433) is enabled and running on the ClearPass appliance. Check via CLI or by attempting to reach the interface.Affected if The web management interface is enabled and accessible.
-
Assess network exposure of management interfaceDetermine if the web management interface is exposed to untrusted networks or the internet. Review firewall rules and access control lists protecting the ClearPass management ports.Affected if The interface is reachable from networks accessible to untrusted or unauthorized users, increasing exploitation risk.
You are affected if ClearPass Policy Manager version 6.9.0-6.9.11 or 6.10.0-6.10.6 is running with its web management interface enabled and accessible in your environment.
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 ClearPass Policy Manager to a version newer than 6.10.6 (for 6.10.x) or 6.9.11 (for 6.9.x) as released by Aruba.
ClearPass Policy Manager 6.9.12 or later (6.9.x line); 6.10.7 or later (6.10.x line)
- 1. Identify the currently installed ClearPass Policy Manager version via the web UI or CLI
- 2. For versions 6.9.x: upgrade to ClearPass Policy Manager 6.9.12 or later
- 3. For versions 6.10.x: upgrade to ClearPass Policy Manager 6.10.7 or later
- 4. After upgrade, verify the new version is running and test that the web-based management interface functions correctly
- 5. Review audit logs to confirm no SQL injection exploitation occurred prior to patching
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-23694 — 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-23694 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