CVE-2021-40989
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 · uneditedA local escalation of privilege vulnerability was discovered in Aruba ClearPass Policy Manager version(s): ClearPass Policy Manager 6.10.x prior to 6.10.2 - - ClearPass Policy Manager 6.9.x prior to 6.9.7-HF1 - - ClearPass Policy Manager 6.8.x prior to 6.8.9-HF1. Aruba has released patches for ClearPass Policy Manager that address this security vulnerability.
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 · moderate confidenceA local privilege escalation vulnerability exists in Aruba ClearPass Policy Manager versions 6.10.x prior to 6.10.2, 6.9.x prior to 6.9.7-HF1, and 6.8.x prior to 6.8.9-HF1. An attacker with local access to the system can exploit this to elevate privileges to higher permission levels.
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.8.0, < 6.8.9>= 6.9.0, < 6.9.7>= 6.10.0, < 6.10.2= 6.8.9= 6.9.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 if Aruba ClearPass Policy Manager is installedLocate the ClearPass Policy Manager installation on the system. Check for the presence of ClearPass-related directories, services, or the product typically installed under /opt or similar installation paths on the host.Affected if ClearPass Policy Manager is present on the system
-
Determine the installed version of ClearPass Policy ManagerRetrieve the installed version number. This can typically be done via the ClearPass CLI using 'show version' or 'appversion' command, or by checking version files in the installation directory if you have filesystem access.Affected if The installed version falls within 6.8.0 to 6.8.9 (inclusive), 6.9.0 to 6.9.7 (inclusive), or 6.10.0 to 6.10.2 (exclusive of 6.10.2)
-
Verify the exact patch levelConfirm whether the installed version is one of the fixed releases: 6.8.9-HF1, 6.9.7-HF1, or 6.10.2. Check the full version string including any HF (hotfix) suffixes.Affected if The version is NOT 6.8.9-HF1, NOT 6.9.7-HF1, and NOT 6.10.2 (these are the patched versions)
-
Assess local access exposureEvaluate whether untrusted local users or attackers could gain access to the system console or command line interface of the ClearPass server.Affected if Local untrusted users have or could obtain command line access to the ClearPass server
You are affected if ClearPass Policy Manager is installed with a version in the ranges 6.8.0 through 6.8.9, 6.9.0 through 6.9.7, or 6.10.0 through 6.10.1, and untrusted local users can access the system.
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.8.96.9.76.10.2
Apply the available patches: upgrade to ClearPass Policy Manager 6.10.2, 6.9.7-HF1, or 6.8.9-HF1 as appropriate for your current version branch.
ClearPass Policy Manager 6.10.2+ (or 6.9.7-HF1+, or 6.8.9-HF1+ depending on your major version branch)
- 1. Identify the currently installed ClearPass Policy Manager version using the WebUI (Dashboard > Overview) or CLI (show version)
- 2. For version 6.8.x: Upgrade to ClearPass Policy Manager 6.8.9-HF1 or later
- 3. For version 6.9.x: Upgrade to ClearPass Policy Manager 6.9.7-HF1 or later
- 4. For version 6.10.x: Upgrade to ClearPass Policy Manager 6.10.2 or later
- 5. Download the appropriate upgrade image from the Aruba support portal (https://asp.arubanetworks.com)
- 6. Back up the current configuration via ClearPass WebUI (Administration > Server Manager > Server Configuration > Backup)
- 7. Upload and install the upgrade following Aruba's upgrade documentation
- 8. After upgrade, verify the version and ensure ClearPass services are running normally
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-2021-40989 — 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-2021-40989 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