dbcve.org
Unified Communications Domain ManagerApplication · Cisco

CVE-2015-0699

MEDIUM · 5.0 CVSS v2.0 Published 2015-04-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges 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
SQL injection vulnerability in the Interactive Voice Response (IVR) component in Cisco Unified Communications Manager (UCM) 10.5(1.98991.13) allows remote attackers to execute arbitrary SQL commands via unspecified vectors, aka Bug ID CSCut21563.

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

SQL injection vulnerability in the Interactive Voice Response (IVR) component of Cisco Unified Communications Manager allows remote attackers to execute arbitrary SQL commands. The vulnerability is in a voice/communication system rather than a traditional web application, suggesting the IVR interface accepts user input that is not properly sanitized before being used in SQL queries.

MitigationApply the Cisco patch for bug ID CSCut21563 when available, or implement input validation/sanitization on the IVR interface as an interim control. Consider network segmentation to limit exposure of the UCM IVR component to untrusted networks.

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:= 10.5\(1.98991.13\)

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
Partial
Integrity
None
Availability
None

AV:N/AC:L/Au:N/C:P/I:N/A:N

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 the installed version of Cisco Unified Communications Manager
    Access the Cisco Unified Communications Administration interface and navigate to System > Version, or run 'show version' via CLI on the UCM server. Alternatively, check the about page in the administration console.
    Affected if The installed version matches 10.5(1.98991.13)
  2. Confirm the Unified Communications Domain Manager version
    Access the Cisco Unified Communications Domain Manager admin interface and locate the version information, typically found in the About or System Information section.
    Affected if The installed version matches 10.5(1.98991.13)
  3. Determine if IVR feature is enabled
    In the Cisco Unified Communications Administration console, navigate to Device > Device Settings > IVR Settings, or check the service parameters for the IVR service. Verify if the IVR subsystem is configured and active.
    Affected if IVR is enabled and configured as an active service
  4. Assess network exposure of the IVR interface
    Review firewall rules and access control lists to determine if the IVR ports (typically TCP 5060 and related SIP/RTP ports) are accessible from untrusted networks. Check if the IVR is reachable from outside the internal network.
    Affected if The IVR interface is accessible from untrusted or external networks
  5. Review system logs for SQL injection indicators
    Examine Cisco UCM RTMT (Real-Time Monitoring Tool) logs, SQL database logs, and system event logs for suspicious SQL syntax, unusual database queries, or authentication anomalies related to the IVR service.
    Affected if Logs contain unexpected SQL commands or query patterns originating from IVR inputs

You are affected if your Cisco Unified Communications Manager or Domain Manager is version 10.5(1.98991.13) AND the IVR component is enabled and exposed, particularly to untrusted networks.

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

Apply the Cisco patch for bug ID CSCut21563 when available, or implement input validation/sanitization on the IVR interface as an interim control. Consider network segmentation to limit exposure of the UCM IVR component to untrusted networks.

Fix this in Unified Communications Domain Manager Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA6.0 h
42.0 hours of engineering $7,360
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-0699 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-0699 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