dbcve.org
ClearpassApplication · Arubanetworks

CVE-2014-5342

HIGH · 10.0 CVSS v2.0 Published 2014-11-19
Fix available
A fix is available. Upgrade to after 6.3.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Aruba Networks ClearPass before 6.3.5 and 6.4.x before 6.4.1 allows remote attackers to execute arbitrary commands via unspecified vectors, a different vulnerability than CVE-2014-6627.

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

Aruba Networks ClearPass Policy Manager contains a command injection vulnerability allowing remote unauthenticated attackers to execute arbitrary OS commands. The vulnerability affects versions before 6.3.5 and 6.4.x before 6.4.1. With a CVSS score of 10, this is a critical flaw requiring immediate remediation.

MitigationUpgrade Aruba ClearPass to version 6.3.5 or 6.4.1 or later to patch the command injection vulnerability. This is a critical infrastructure system so upgrade should be performed in a controlled maintenance window with rollback capability.

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
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/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. Identify the installed ClearPass version
    Access the ClearPass Policy Manager admin interface or use the system console to retrieve the current software version. This is typically found in the About or System Information section of the admin UI, or via CLI command if available.
    Affected if The displayed version is 6.3.4 or earlier, or exactly version 6.4.0
  2. Compare version against affected ranges
    Review the version number obtained from the system against the known vulnerable versions: any build at or below 6.3.4, or specifically version 6.4.0.
    Affected if The installed version falls within <= 6.3.4 or equals exactly 6.4.0
  3. Assess network exposure of the ClearPass management interface
    Determine if the ClearPass Policy Manager web interface or API endpoints are reachable from untrusted networks or the public internet.
    Affected if The management interface is exposed to untrusted networks, enabling the remote unauthenticated attack vector
  4. Verify if the guest self-service portal is enabled
    Check whether the ClearPass Guest or self-service portal functionality is configured and active, as command injection may occur in these unauthenticated components.
    Affected if Guest or self-service portals are enabled and accessible without authentication

The environment is affected if the installed ClearPass Policy Manager version is 6.3.4 or earlier, or exactly 6.4.0, and the vulnerable interface is network-accessible.

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 Aruba ClearPass to version 6.3.5 or 6.4.1 or later to patch the command injection vulnerability. This is a critical infrastructure system so upgrade should be performed in a controlled maintenance window with rollback capability.

Recommended fix High confidence

ClearPass 6.3.5 or 6.4.1 (depending on your current branch)

  1. Identify the current Clearpass version by accessing the ClearPass admin UI or CLI
  2. If running Clearpass version <= 6.3.4, plan upgrade to version 6.3.5 or later
  3. If running Clearpass version 6.4.0 or 6.4.x before 6.4.1, plan upgrade to version 6.4.1 or later
  4. Review Aruba Networks release notes for upgrade prerequisites and procedures
  5. Execute the upgrade following Aruba's documented upgrade process
  6. After upgrade, verify the ClearPass services are running correctly
  7. Confirm the new version is 6.3.5 or higher, or 6.4.1 or higher
Caveat Major version upgrades may have compatibility considerations; review Aruba release notes for any configuration or feature changes

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

Fix this in Clearpass Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Check whether your project pulls in CVE-2014-5342 — 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-5342 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