CVE-2014-8367
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 · uneditedSQL injection vulnerability in Aruba Networks ClearPass Policy Manager (CPPM) 6.2.x, 6.3.x before 6.3.6, and 6.4.x before 6.4.2 allows remote attackers to execute arbitrary SQL commands 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 · high confidenceSQL injection vulnerability in Aruba Networks ClearPass Policy Manager allows remote attackers to execute arbitrary SQL commands via unspecified vectors. The flaw affects versions 6.2.x, 6.3.x before 6.3.6, and 6.4.x before 6.4.2, enabling unauthenticated attackers to manipulate database queries.
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.2.0, <= 6.2.6>= 6.3.0, < 6.3.6>= 6.4.0, < 6.4.2= 6.2CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 version via web interfaceLog into the ClearPass Policy Manager admin web interface and navigate to Administration > Server Manager > Server Configuration. Record the installed version number shown.Affected if The displayed version falls within 6.2.0 through 6.2.6, 6.3.0 through 6.3.5, or 6.4.0 through 6.4.1.
-
Identify ClearPass Policy Manager version via CLIAccess the ClearPass server console or SSH and run the command 'show version' or 'cat /etc/version' to retrieve the installed version.Affected if The version output falls within the affected ranges 6.2.0-6.2.6, 6.3.0-6.3.5, or 6.4.0-6.4.1.
-
Verify HTTP/HTTPS access to ClearPass Policy Manager is exposedConfirm that the ClearPass Policy Manager web interface (ports 80/443 or custom SSL port) is reachable from network segments where untrusted users could send HTTP requests.Affected if The web interface is externally accessible or accessible from untrusted network segments without additional filtering.
-
Confirm the guest self-service portal is enabledCheck if the ClearPass Guest or Self-Service portal is enabled under Configuration > Authentication > Guest. This feature often exposes the unauthenticated SQL injection entry point.Affected if The guest or self-service portal is enabled and reachable without authentication.
The system is affected if the installed ClearPass Policy Manager version is 6.2.x, 6.3.x before 6.3.6, or 6.4.x before 6.4.2, and the web interface or guest portal is accessible.
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.3.66.4.2
Upgrade Aruba ClearPass Policy Manager to version 6.3.6 or later (for 6.3.x) or 6.4.2 or later (for 6.4.x), or apply appropriate patch if available from Aruba Networks.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8367 — 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-2014-8367 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