Clearpass Policy ManagerApplication · Arubanetworks

CVE-2022-43530

HIGH · 8.8 CVSS v3.1 Published 2023-01-05
Fix available
A fix is available. Upgrade to 6.9.12 / 6.10.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Vulnerabilities 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 confidence

SQL 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.

MitigationUpgrade 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.

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
Clearpass Policy ManagerApplication
Affected:>= 6.9.0, < 6.9.12>= 6.10.0, < 6.10.7

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Aruba ClearPass Policy Manager is installed
    Check 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.
  2. Determine installed version of ClearPass Policy Manager
    Log 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.
  3. Compare version against affected ranges
    Check 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.
  4. Verify web-based management interface is accessible
    Confirm 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.
  5. Check for user authentication configuration
    Review 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.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 6.9.12 / 6.10.7 or later
Fixed in 6.9.126.10.7
Interim mitigation

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.

Recommended fix High confidence

ClearPass Policy Manager 6.9.13 (for 6.9.x branch) or 6.10.8 (for 6.10.x branch)

  1. 1. Backup the ClearPass Policy Manager configuration before initiating any upgrade.
  2. 2. Review the ClearPass Policy Manager upgrade guide for prerequisites and compatibility requirements.
  3. 3. For users on 6.9.x branch: upgrade to ClearPass Policy Manager 6.9.13 or later.
  4. 4. For users on 6.10.x branch: upgrade to ClearPass Policy Manager 6.10.8 or later.
  5. 5. After upgrade, verify the web-based management interface is accessible and all services are running.
  6. 6. Test critical authentication and policy enforcement workflows to confirm normal operation.
Caveat Ensure compatibility with any integrated systems and review upgrade notes for potential configuration changes required post-upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Clearpass Policy Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-43530 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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