dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2014-0734

HIGH · 7.5 CVSS v2.0 Published 2014-02-20
Fix available
A fix is available. Upgrade to after 10.0 or later.
See remediation →
84/100
Remediation priority · High
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 Certificate Authority Proxy Function (CAPF) implementation in Cisco Unified Communications Manager (Unified CM) 10.0(1) and earlier allows remote attackers to execute arbitrary SQL commands via a crafted URL, aka Bug ID CSCum46483.

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 Cisco Unified Communications Manager's Certificate Authority Proxy Function (CAPF) allows remote attackers to execute arbitrary SQL commands via crafted URLs. The CAPF component handles certificate operations for IP phones and other UC devices. This is a classic SQL injection flaw in the web interface of the Unified CM version 10.0(1) and earlier.

MitigationApply the Cisco security patch for bug ID CSCum46483. Until patched, restrict network access to Unified CM management interfaces and disable CAPF if not required.

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:<= 10.0\(1\)= 3.3\(5\)= 3.3\(5\)sr1= 3.3\(5\)sr2a= 4.1\(3\)= 4.1\(3\)sr1= 4.1\(3\)sr2= 4.1\(3\)sr3= 4.1\(3\)sr4= 4.2= 4.2.1= 4.2.2

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

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

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

  1. Identify the installed Cisco Unified Communications Manager version
    Log into the Cisco Unified CM Administration interface and navigate to About > Version, or use the CLI command 'show version' via SSH to retrieve the exact version number
    Affected if The installed version is 10.0(1) or any earlier version, or matches 3.3(5), 3.3(5)sr1, 3.3(5)sr2a, 4.1(3), 4.1(3)sr1, 4.1(3)sr2, 4.1(3)sr3, 4.1(3)sr4, 4.2, 4.2.1, or 4.2.2
  2. Verify if the CAPF service is enabled
    In the Cisco Unified CM Administration interface, go to System > Service Parameters and check the status of the Certificate Authority Proxy Function (CAPF) service, or use the CLI command 'show service' to list running services
    Affected if CAPF is enabled and running on the system
  3. Confirm web interface accessibility for CAPF
    Attempt to access the CAPF web interface URL (typically https://<ucm_host>/capf) from a network location, or verify that the web interface port (usually 8443) is listening and reachable
    Affected if The CAPF web interface is reachable from network locations where attackers could send crafted HTTP requests
  4. Check for recent security patches
    Review the installed patches on the system via the Cisco Unified CM RTMT (Real-Time Monitoring Tool) or check the patch history in the Administration interface under Software Upgrades > Install/Upgrade
    Affected if The system is missing the patch for bug ID CSCum46483, which is the specific fix for this SQL injection vulnerability

The environment is affected if Cisco Unified Communications Manager is running a version listed in the affected ranges AND the CAPF service is enabled with its web interface accessible.

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
Upgrade available Upgrade to a release after 10.0
Interim mitigation

Apply the Cisco security patch for bug ID CSCum46483. Until patched, restrict network access to Unified CM management interfaces and disable CAPF if not required.

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 the upgrade done

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-0734 — 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-2014-0734 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