CVE-2022-43531
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 vulnerabilities in the web-based management interface of ClearPass Policy Manager allow authenticated remote attackers to inject malicious SQL queries, potentially exposing or modifying sensitive database information and leading to 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 the installed ClearPass Policy Manager versionLog into the ClearPass CLI or access the web-based management interface and navigate to the About or Administration > Server Manager > Server Information section to retrieve the exact version number (for example, '6.10.x' or '6.9.x').Affected if The installed version falls within 6.9.0 to 6.9.11 OR 6.10.0 to 6.10.6 (any version >= 6.9.0 but < 6.9.12, or >= 6.10.0 but < 6.10.7). Compare your version against these vulnerable ranges.
-
Confirm the web-based management interface is enabledCheck the ClearPass configuration or network settings to determine if the web-based management interface (HTTP/HTTPS on port 443 or 80) is exposed and accessible from the network.Affected if The web-based management interface is enabled and reachable over the network, as the SQL injection flaw resides in this component.
-
Verify the presence of an attacker with valid credentialsReview Access Tracker logs, audit logs, or user session records within the ClearPass web interface (under Monitoring > Troubleshooting > Access Tracker) for any unexpected or unauthorized user logins that may have occurred.Affected if An unauthorized or suspicious user account was used to log into the management interface, as authentication is required to exploit the SQL injection vulnerability.
-
Inspect database query logs for anomaliesExamine ClearPass logs for any abnormal or unexpected SQL syntax within API requests, particularly in areas where the web interface accepts user input (for example, search filters, report parameters, or configuration fields).Affected if Logs contain SQL-like syntax or errors that suggest injection attempts were made against the management interface.
Your ClearPass Policy Manager is affected if the installed version is 6.9.0 through 6.9.11 or 6.10.0 through 6.10.6 AND the web-based management interface is accessible to an authenticated attacker who could inject malicious SQL queries.
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 (for 6.10.x branches) or 6.9.13 or higher (for 6.9.x branches) per Aruba's official security advisory.
ClearPass Policy Manager 6.9.12 or later (6.9.x branch); ClearPass Policy Manager 6.10.7 or later (6.10.x branch)
- Identify the currently installed ClearPass Policy Manager version by navigating to Administration » About in the web interface
- For ClearPass Policy Manager 6.9.x: Plan an upgrade to version 6.9.12 or later
- For ClearPass Policy Manager 6.10.x: Plan an upgrade to version 6.10.7 or later
- Review Aruba upgrade documentation and release notes for upgrade procedures
- Ensure adequate backups of configuration and data are performed before upgrading
- Schedule maintenance window as upgrades may require service restart
- Execute upgrade following Aruba's documented upgrade procedure
- After upgrade, verify the new version is installed and the SQL injection vulnerability is remediated
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-43531 — 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-43531 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