dbcve.org
ClearpassApplication · Arubanetworks

CVE-2014-6625

HIGH · 9.0 CVSS v2.0 Published 2014-11-19
Fix available
A fix is available. Upgrade to after 6.3.4 or later.
See remediation →
96/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
The Policy Manager in Aruba Networks ClearPass before 6.3.6 and 6.4.x before 6.4.1 allows remote authenticated users to gain privileges via unspecified vectors.

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 confidence

This is a privilege escalation vulnerability in the Aruba Networks ClearPass Policy Manager. Remote authenticated users can gain elevated privileges through unspecified vectors, potentially allowing them to access administrative functions beyond their assigned role. The vulnerability affects versions before 6.3.6 and 6.4.x before 6.4.1.

MitigationUpgrade ClearPass Policy Manager to version 6.3.6 or 6.4.1 or later to remediate this vulnerability. Ensure proper access controls are maintained and monitor for any unauthorized privilege escalation attempts.

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
ClearpassApplication
Affected:<= 6.3.4= 6.4.0

CVSS 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
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:S/C:C/I:C/A:C

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 checks

Work through these to decide whether this CVE applies to you.

  1. Locate ClearPass Policy Manager installation
    Identify all ClearPass Policy Manager servers in your environment. Check for the 'ClearPass' or 'CPPM' service running on your network. The application is typically deployed on Linux or as a virtual appliance.
    Affected if ClearPass Policy Manager is present in the environment
  2. Determine installed version
    Access the ClearPass Policy Manager admin interface or check the system via CLI. Navigate to Administration > About or use the command line to retrieve the exact version number (for example, 'show version' or check /var/lib/clearpass/VERSION if accessible).
    Affected if The version cannot be determined or is not visible
  3. Compare version against affected ranges
    Compare your installed version to these affected ranges: versions 6.3.4 and earlier, or version 6.4.0 specifically. Also note that versions 6.3.5 and 6.4.0 are affected, while 6.3.6 and 6.4.1 and later are fixed.
    Affected if Installed version is 6.3.4 or lower, or installed version is exactly 6.4.0
  4. Check for remote authentication access
    Review user authentication logs and access controls. Determine if there are any externally-facing authentication portals or API endpoints that allow remote user logins to ClearPass Policy Manager.
    Affected if Remote authentication is enabled and users can authenticate to ClearPass from outside the local network
  5. Audit user role assignments
    Review the administrative roles and privileges assigned to non-admin users in ClearPass Policy Manager. Check if any users have privileges beyond what they were originally assigned, which could indicate exploitation.
    Affected if Users have elevated privileges that were not intentionally assigned to them

You are affected if ClearPass Policy Manager version is 6.3.4 or lower, or exactly 6.4.0, and remote authenticated users exist in the environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 6.3.4
Interim mitigation

Upgrade ClearPass Policy Manager to version 6.3.6 or 6.4.1 or later to remediate this vulnerability. Ensure proper access controls are maintained and monitor for any unauthorized privilege escalation attempts.

Recommended fix High confidence

ClearPass 6.3.6 or 6.4.1 (depending on your target major version branch)

  1. Review the Aruba ClearPass upgrade guide and release notes for version 6.3.6 or 6.4.1
  2. Ensure you have a complete backup of the current ClearPass configuration
  3. Schedule a maintenance window for the upgrade process
  4. Download the appropriate upgrade image (6.3.6 or 6.4.1) from the Aruba support portal
  5. Follow Aruba's documented upgrade procedure for ClearPass Policy Manager
  6. After upgrade, verify the Policy Manager is functioning correctly
  7. Confirm the version number matches the expected fixed release
Caveat Standard upgrade precautions apply - review release notes for any configuration or behavioral changes before proceeding

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Clearpass Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-6625 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-6625 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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