dbcve.org
ClearpassApplication · Arubanetworks

CVE-2016-2034

CRITICAL · 9.8 CVSS v3.0 Published 2017-06-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
SQL injection vulnerability in ClearPass Policy Manager 6.5.x through 6.5.6 and 6.6.0.

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

SQL injection vulnerability in ClearPass Policy Manager versions 6.5.x through 6.5.6 and 6.6.0. This critical flaw allows unauthenticated attackers to inject malicious SQL queries, potentially compromising the database, extracting sensitive data, or gaining administrative access to the policy manager.

MitigationApply vendor patches beyond version 6.6.0 when available; implement input validation and parameterized queries as a compensating control; consider WAF deployment to filter SQL injection attempts until patching is complete.

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.5.0= 6.5.1= 6.5.2= 6.5.3= 6.5.4= 6.5.5= 6.5.6= 6.6.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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/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 checks

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

  1. Determine ClearPass Policy Manager version
    Access the ClearPass CLI via SSH and run the command 'show version' or 'show system-info'. Alternatively, log into the web interface and check the About or Dashboard page for the software version.
    Affected if The displayed version matches any of these: 6.5.0, 6.5.1, 6.5.2, 6.5.3, 6.5.4, 6.5.5, 6.5.6, or 6.6.0.
  2. Verify ClearPass web interface accessibility
    Confirm that the ClearPass Policy Manager web interface (typically ports 443 or 4433) is reachable from network segments where untrusted users could send requests.
    Affected if The web interface is exposed to untrusted networks without network segmentation or access controls.
  3. Check for SQL injection entry points
    Review web access logs or proxy logs for the ClearPass Policy Manager for unusual or malformed SQL syntax in URL parameters, form inputs, or API endpoints.
    Affected if Unusual SQL-like characters or syntax appear in HTTP requests to ClearPass, indicating possible exploitation attempts.

If the installed ClearPass Policy Manager version is 6.5.0 through 6.5.6 or exactly 6.6.0 and the web interface is network-accessible, the environment is affected by this unauthenticated SQL injection vulnerability.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor patches beyond version 6.6.0 when available; implement input validation and parameterized queries as a compensating control; consider WAF deployment to filter SQL injection attempts until patching is complete.

Recommended fix Moderate confidence

ClearPass Policy Manager 6.5.7 or later (or 6.6.1+ if on 6.6.x branch)

  1. 1. Identify the current ClearPass Policy Manager version running in your environment
  2. 2. Download the latest ClearPass Policy Manager release from Aruba's support portal (https://asp.arubanetworks.com/)
  3. 3. Review Aruba upgrade documentation and release notes for the target version
  4. 4. Create a backup of the current ClearPass configuration
  5. 5. Schedule a maintenance window as upgrades may require downtime
  6. 6. Follow Aruba's documented upgrade procedure for ClearPass Policy Manager
  7. 7. After upgrade, verify the system is functioning correctly and the SQL injection vulnerability is resolved
Caveat Review upgrade documentation for potential compatibility issues and ensure sufficient downtime window

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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