Unified Communications Domain ManagerApplication · Cisco
CVE-2015-0591
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 · uneditedCisco Unified Communications Domain Manager (UCDM) 10 allows remote attackers to cause a denial of service (daemon hang and GUI outage) via a flood of malformed TCP packets, aka Bug ID CSCur44177.
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 confidenceCisco Unified Communications Domain Manager (UCDM) version 10 is vulnerable to a denial of service attack where remote attackers can flood the system with malformed TCP packets, causing the daemon to hang and resulting in complete GUI outage.
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 Domain ManagerApplication
= 10.0CVSS 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 installed UCDM versionAccess the UCDM admin console or use the command line interface (e.g., 'show version' or check system information in the GUI under About/Version) to determine the exact version of Cisco Unified Communications Domain ManagerAffected if The installed version is exactly 10.0 (10.0.0) - note that only version 10.0 is listed as affected, later versions may not be vulnerable
-
Confirm UCDM service is runningCheck if the UCDM daemon/service is active by logging into the UCDM server and running system status commands or checking the service management consoleAffected if The UCDM service daemon is running and responding to requests - only a running service can be hung by malformed packets
-
Verify network exposure of management interfaceCheck firewall rules, network ACLs, or interface bindings to determine if the UCDM management GUI (typically port 443 or 8443) is accessible from untrusted networksAffected if The UCDM management interface is exposed to external/untrusted networks without proper filtering - the vulnerability is exploitable remotely via network packets
A system is affected if it runs exactly version 10.0 of Cisco UCDM with the management interface accessible to network attackers who can send malformed TCP packets.
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 dataDeploy network-level filtering such as firewall rules or intrusion prevention systems to block malformed TCP packets, and implement rate limiting on exposed interfaces to mitigate packet floods.
Fix this in Unified Communications Domain Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0591 — 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-0591 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