CVE-2020-7111
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 server side injection vulnerability exists which could allow an authenticated administrative user to achieve Remote Code Execution in ClearPass. 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 · high confidenceServer-side injection vulnerability in Aruba ClearPass Policy Manager allowing authenticated administrative users to achieve remote code execution. The vulnerability stems from insufficient input validation on the server side, enabling injection of malicious code or commands.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 Policy Manager installationLocate the ClearPass Policy Manager application in your environment. This is typically deployed as a virtual appliance or on-premises server. Check your asset inventory or scan for the ClearPass service.Affected if ClearPass Policy Manager is present in your environment
-
Determine installed ClearPass versionAccess the ClearPass administration UI or check the CLI. The version is typically visible in the login page footer, under About in the help menu, or via CLI command 'show version'. Compare your version to the affected ranges: 6.7.0 through 6.7.12, or 6.8.0 through 6.8.3.Affected if Installed version falls within 6.7.0 to 6.7.12, or 6.8.0 to 6.8.3
-
Verify administrative interface accessibilityConfirm the ClearPass admin web interface (default ports 443 or 8443) is reachable from your network. Check firewall rules and network segmentation around the ClearPass server.Affected if Administrative interface is exposed beyond trusted admin networks
-
Confirm administrative accounts existReview ClearPass user database to verify administrative accounts are configured. The vulnerability requires an authenticated administrative user to exploit the injection flaw.Affected if Any administrative users are provisioned in ClearPass Policy Manager
You are affected if ClearPass Policy Manager version is 6.7.0-6.7.12 or 6.8.0-6.8.3 and the admin interface is accessible with valid administrative credentials.
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.
From vendor data6.7.136.8.4
Upgrade ClearPass to version 6.7.13, 6.8.4, 6.9.0 or higher. Apply principle of least privilege to administrative accounts until patching is complete.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7111 — 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-7111 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