Unified Communications ManagerApplication · Cisco
CVE-2015-6425
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 · uneditedThe WebApplications Identity Management subsystem in Cisco Unified Communications Manager 10.5(0.98000.88) allows remote attackers to cause a denial of service (subsystem outage) via invalid session tokens, aka Bug ID CSCul83786.
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 confidenceThe WebApplications Identity Management subsystem in Cisco Unified Communications Manager 10.5(0.98000.88) contains a denial-of-service vulnerability where processing invalid session tokens causes the subsystem to crash, resulting in an outage. Remote attackers can exploit this without authentication by sending specially crafted requests with malformed session tokens.
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
Unified Communications ManagerApplication
= 10.5\(0.98000.88\)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
- None
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:N/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 the Cisco Unified Communications Manager versionLog into the Cisco Unified Communications Manager Administration interface and navigate to 'System > Version' or run the 'show version' command from the admin CLIAffected if The displayed version is exactly 10.5(0.98000.88)
-
Confirm the exact build numberLocate the full version string in the admin interface or CLI output, ensuring it shows 10.5(0.98000.88) specifically - do not assume partial matches indicate the same buildAffected if The version string matches 10.5(0.98000.88) exactly with no additional build identifiers
-
Verify the WebApplications Identity Management subsystem is runningFrom the Cisco Unified Communications Manager Serviceability interface, navigate to 'Tools > Service Activation' and confirm the 'WebApplications' service is activated, or use the CLI command 'show service' to list running servicesAffected if The WebApplications service is activated and running on the affected CUCM server
A user is affected only if their Cisco Unified Communications Manager is running exactly version 10.5(0.98000.88) AND the WebApplications Identity Management subsystem is enabled and active.
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 dataApply the Cisco patch for bug ID CSCul83786 or upgrade to a Cisco Unified Communications Manager version that includes the fix. Prior to deployment, establish rollback procedures and test in a non-production environment.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6425 — 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-2015-6425 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