Unified Communications Domain ManagerApplication · Cisco

CVE-2015-0682

MEDIUM · 6.5 CVSS v2.0 Published 2015-04-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Cisco Unified Communications Domain Manager 8.1(4) allows remote authenticated users to execute arbitrary code by visiting a "deprecated page," aka Bug ID CSCup90168.

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

A remote code execution vulnerability exists in Cisco Unified Communications Domain Manager 8.1(4) where a deprecated administrative page does not properly sanitize user input, allowing authenticated remote attackers to execute arbitrary code on the underlying system.

MitigationIdentify and disable or remove the deprecated page (CSCup90168), or apply the vendor patch from Cisco for version 8.1(4). If the deprecated functionality is still required, implement strict access controls and input validation until a patch can be applied.

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
Affected:= 8.1\(.4\)

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
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/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 checks

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

  1. Identify installed Cisco Unified Communications Domain Manager version
    Access the administrative interface or use the system management console to retrieve the product version. Typically found in 'About' or 'System Information' section of the management portal, or via CLI command 'show version' if available.
    Affected if The installed version is exactly 8.1(4)
  2. Confirm the deprecated administrative page exists
    Check for the presence of the page associated with Cisco bug ID CSCup90168. This is typically a legacy admin page that should have been removed or disabled. Consult system documentation or examine the web application directory structure for deprecated admin endpoints.
    Affected if The deprecated page (CSCup90168) is present and accessible on the system
  3. Verify administrative interface authentication status
    Examine the authentication configuration for the administrative web interface. Determine if the deprecated page enforces proper authentication or if it can be accessed without full credential validation.
    Affected if The deprecated page allows authenticated access but does not properly sanitize user input for code execution
  4. Check for exposure of administrative interfaces
    Review network accessibility of the management interface. Determine if the admin portal is exposed to network segments beyond the trusted internal network.
    Affected if The administrative interface is accessible from less-trusted network segments

The environment is affected if Cisco Unified Communications Domain Manager version 8.1(4) is running and the deprecated administrative page (CSCup90168) remains accessible on the system.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Identify and disable or remove the deprecated page (CSCup90168), or apply the vendor patch from Cisco for version 8.1(4). If the deprecated functionality is still required, implement strict access controls and input validation until a patch can be applied.

Fix this in Unified Communications Domain Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0682 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-0682 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