Unified Communications Domain ManagerApplication · Cisco
CVE-2015-0588
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 · uneditedCross-site request forgery (CSRF) vulnerability in Cisco Unified Communications Domain Manager (UCDM) 10 allows remote attackers to hijack the authentication of arbitrary users, aka Bug ID CSCuo77055.
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 confidenceCross-site request forgery (CSRF) vulnerability in Cisco Unified Communications Domain Manager (UCDM) 10 allows remote attackers to hijack the authentication of arbitrary users by tricking authenticated users into submitting malicious requests to the application.
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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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 Cisco UCDM versionAccess the Cisco UCDM administrative web interface and navigate to About or System Information section to find the exact version number. Alternatively, check the software release notes or the installed package version if you have CLI access.Affected if The installed version is exactly 10.0 (Cisco UCDM 10.0)
-
Inspect web form submissions for anti-CSRF tokensLog into the UCDM web application, open browser developer tools, and examine the HTML source of state-changing forms (such as user management, configuration settings). Look for hidden input fields containing anti-CSRF tokens or session tokens.Affected if Forms lack anti-CSRF tokens in hidden fields - the vulnerability exists when forms can be submitted without token validation
-
Verify SameSite cookie attributesIn browser developer tools, inspect cookies set by the UCDM application. Check the Set-Cookie headers for SameSite attribute values.Affected if Cookies do not have SameSite attribute set (or it is set to None/Lax without Secure flag), indicating missing CSRF protection
-
Check Origin/Referer header handlingSubmit a test request from an external domain (or simulate via proxy) and observe if the application rejects requests with missing or mismatched Origin/Referer headers.Affected if The application accepts requests without validating Origin or Referer headers, allowing cross-origin forged requests
A user is affected if running Cisco UCDM version 10.0 and the application lacks anti-CSRF tokens in web forms, SameSite cookie attributes, and Origin/Referer header validation.
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 dataImplement anti-CSRF tokens on all state-changing operations, validate Origin/Referer headers, and enforce SameSite cookie attributes to prevent authentication hijacking.
Fix this in Unified Communications Domain Manager
Scoped from the published advisory
- Consultation6.0 h
- Implementation30.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $15,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-0588 — 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-0588 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