CVE-2017-5829
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 · uneditedAn access restriction bypass vulnerability in HPE Aruba ClearPass Policy Manager version 6.6.x was found.
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 · low confidenceAn access restriction bypass vulnerability exists in HPE Aruba ClearPass Policy Manager version 6.6.x. The vulnerability allows authenticated or unauthenticated users to circumvent access control policies that should restrict access to certain resources or functions within the policy management system.
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.6.0, < 6.6.5CVSS 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.0/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 installed ClearPass Policy Manager versionLog into the ClearPass admin web interface and navigate to Administration > Server Management > Server Configuration, or run 'show version' via CLI to retrieve the exact software version numberAffected if The displayed version is 6.6.0, 6.6.1, 6.6.2, 6.6.3, or 6.6.4 (any version >= 6.6.0 but < 6.6.5)
-
Confirm ClearPass web service is accessibleVerify that the ClearPass Policy Manager web interface (HTTPS port 443 or custom configured port) is reachable from network locations where the access bypass could be exploitedAffected if The web interface or API endpoints are exposed to network segments containing untrusted users
-
Review access control policy configurationsNavigate to Configuration > Access Policy in the ClearPass admin console and examine the policy rules that restrict access to sensitive resources or administrative functionsAffected if Policies exist that should restrict access based on user roles, authentication status, or network zone but may be circumvented due to this vulnerability
-
Audit recent authentication and authorization eventsReview ClearPass accounting and audit logs under Monitoring > Live Monitoring > Authenticated Sessions for any unusual access patterns or unauthorized resource access attempts that may indicate exploitationAffected if Logs show successful access to restricted resources by users or sessions that should have been denied by policy rules
Your environment is affected if ClearPass Policy Manager version is 6.6.0 through 6.6.4 and the web interface is network-accessible, regardless of whether access control policies are configured.
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.6.5
Upgrade to a patched version of Aruba ClearPass Policy Manager that addresses this vulnerability. Refer to the official HPE Aruba security bulletin for the specific fixed version number.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5829 — 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-2017-5829 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