CVE-2022-43530
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): ClearPass Policy Manager 6.10.x: 6.10.7 and below and ClearPass Policy Manager 6.9.x: 6.9.12 and below.
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 vulnerability in the web-based management interface of Aruba ClearPass Policy Manager allows authenticated remote attackers to inject malicious SQL queries, potentially exposing or modifying sensitive database information and compromising the entire 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.
-
Confirm Aruba ClearPass Policy Manager is installedCheck the system for ClearPass Policy Manager by reviewing installed packages, running processes, or checking the management interface URL. Common paths include / Clearpass or the service may be listening on port 443/4433.Affected if ClearPass Policy Manager software is not present on the system.
-
Determine installed version of ClearPass Policy ManagerLog into the web-based management interface and navigate to Administration > About, or run 'show version' via CLI if you have console access. The version number will be displayed.Affected if Unable to retrieve version information.
-
Compare version against affected rangesCheck if the installed version falls within: 6.9.0 through 6.9.11, or 6.10.0 through 6.10.6. Versions 6.9.12+ and 6.10.7+ are fixed.Affected if Version is >= 6.9.0 and < 6.9.12, or >= 6.10.0 and < 6.10.7.
-
Verify web-based management interface is accessibleConfirm the ClearPass web interface is reachable over the network. This is typically accessible via HTTPS on port 443 or 4433.Affected if Web interface is accessible externally or to untrusted networks.
-
Check for user authentication configurationReview which user accounts have administrative access to ClearPass. The SQL injection requires a valid authenticated session.Affected if Administrative or operator accounts exist in the system, particularly if they are accessible to remote users.
A system is affected if it runs ClearPass Policy Manager versions 6.9.0-6.9.11 or 6.10.0-6.10.6 and has the web-based management interface accessible to authenticated users.
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 version 6.10.8 or higher, or 6.9.13 or higher. Apply the latest security patches from Aruba and follow their upgrade documentation.
ClearPass Policy Manager 6.9.13 (for 6.9.x branch) or 6.10.8 (for 6.10.x branch)
- 1. Backup the ClearPass Policy Manager configuration before initiating any upgrade.
- 2. Review the ClearPass Policy Manager upgrade guide for prerequisites and compatibility requirements.
- 3. For users on 6.9.x branch: upgrade to ClearPass Policy Manager 6.9.13 or later.
- 4. For users on 6.10.x branch: upgrade to ClearPass Policy Manager 6.10.8 or later.
- 5. After upgrade, verify the web-based management interface is accessible and all services are running.
- 6. Test critical authentication and policy enforcement workflows to confirm normal operation.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-43530 — 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-43530 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