CVE-2020-7114
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 vulnerability exists allowing attackers, when present in the same network segment as ClearPass' management interface, to make changes to certain databases in ClearPass by crafting HTTP packets. As a result of this attack, a possible complete cluster compromise might occur. Resolution: Fixed in 6.7.13, 6.8.4, 6.9.0 and higher.
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 network-based vulnerability in Aruba ClearPass allows attackers on the same network segment as the management interface to craft malicious HTTP packets that modify certain databases, potentially leading to complete 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.7.0, < 6.7.13>= 6.8.0, < 6.8.4CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 installationCheck if Aruba ClearPass is deployed in your environment by reviewing installed software or consulting your asset inventory. ClearPass is typically deployed as a virtual appliance or hardware appliance for policy management.Affected if ClearPass is not installed - you are not affected
-
Determine installed ClearPass versionLog into the ClearPass administration UI or access the CLI and retrieve the version information. In the UI: Help > About. Via CLI: execute 'show version' or 'show chassis'Affected if Version is less than 6.7.13 or between 6.8.0 and 6.8.3 (inclusive) - you may be affected
-
Verify management interface network exposureReview your network configuration to determine what networks can reach the ClearPass management interface (default ports: TCP 443, TCP 80). Check firewall rules, ACLs, or network segmentation policies protecting the management interface.Affected if Management interface is reachable from untrusted or non-administrative network segments - you are potentially affected if version is vulnerable
-
Confirm database modification accessThis check requires understanding if the HTTP interface for database modifications is accessible. Review any web application firewall logs or proxy logs for suspicious POST requests to database manipulation endpoints.Affected if Unrestricted HTTP access exists to the management interface from untrusted networks - you are at higher risk
You are affected if ClearPass is installed with version 6.7.0-6.7.12 or 6.8.0-6.8.3 AND the management interface is accessible from untrusted network segments.
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.7.136.8.4
Primary remediation is upgrading to fixed versions (6.7.13, 6.8.4, 6.9.0+). As a compensating control, network segmentation should restrict access to the management interface to only trusted administrative networks.
Upgrade to ClearPass 6.7.13, 6.8.4, or 6.9.0+ (latest stable release)
- 1. Determine the current ClearPass version by navigating to the ClearPass Policy Manager web UI and checking the Dashboard or by running 'show version' in the CLI
- 2. Based on current version, select target fixed release: if running 6.7.x upgrade to 6.7.13; if running 6.8.x upgrade to 6.8.4; alternatively upgrade to 6.9.0 or latest stable release
- 3. Create a full backup of the ClearPass configuration from the Administration > Backup page in the web UI
- 4. Download the upgrade image from the Aruba Support Portal (requires valid support contract)
- 5. Upload the upgrade image via the ClearPass web UI under Administration > Software Update > Upload Upgrade Image
- 6. Initiate the upgrade process and allow sufficient time for completion (this may take 15-30 minutes)
- 7. After upgrade completes, verify the new version is running by checking the Dashboard
- 8. Confirm the upgrade was successful and the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7114 — 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-2020-7114 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