Unified Communications ManagerApplication · Cisco

CVE-2014-3366

MEDIUM · 6.5 CVSS v2.0 Published 2014-10-31
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
SQL injection vulnerability in the administrative web interface in Cisco Unified Communications Manager allows remote authenticated users to execute arbitrary SQL commands via a crafted response, aka Bug ID CSCup88089.

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 · high confidence

SQL injection vulnerability in the administrative web interface of Cisco Unified Communications Manager allows authenticated remote attackers to execute arbitrary SQL commands via crafted input parameters.

MitigationApply Cisco security patches for Bug ID CSCup88089; if unavailable, restrict administrative web interface access to trusted networks and implement strict input validation at the application layer.

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
Affected:all versions

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 if Cisco Unified Communications Manager is installed
    Check for CUCM-related processes or services running on the system, or review installed software listings for Cisco Unified Communications Manager or CUCM components
    Affected if Cisco Unified Communications Manager is present on the system
  2. Determine if the administrative web interface is accessible
    Check if ports used by CUCM admin interface (typically 8443, 443, or 8080) are listening and reachable on the system or network
    Affected if The administrative web interface is exposed and reachable
  3. Verify network access to the admin web interface
    Assess whether the CUCM admin interface is accessible from untrusted networks or externally, rather than only from trusted management networks
    Affected if The admin interface can be accessed from networks outside the trusted administrative zone
  4. Confirm authentication is enabled for the web interface
    Verify that the CUCM admin web interface requires authentication (this is required for the SQL injection to be exploitable)
    Affected if Authentication is required to access the admin interface (which is the normal configuration, making the flaw exploitable by any valid credential holder)
  5. Check for security patches
    Contact Cisco support or review CUCM system status to determine if patches for CSCup88089 have been applied
    Affected if Patches for CSCup88089 have not been applied to the installed CUCM version

The environment is affected if Cisco Unified Communications Manager is installed, its administrative web interface is accessible (even to authenticated users only), and the CSCup88089 patches have not been applied.

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 Cisco security patches for Bug ID CSCup88089; if unavailable, restrict administrative web interface access to trusted networks and implement strict input validation at the application layer.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3366 — 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-2014-3366 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