dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2014-0747

MEDIUM · 6.8 CVSS v2.0 Published 2014-02-27
Fix available
A fix is available. Upgrade to after 10.0 or later.
See remediation →
70/100
Remediation priority · Elevated
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
The Certificate Authority Proxy Function (CAPF) CLI implementation in Cisco Unified Communications Manager (Unified CM) 10.0(1) and earlier allows local users to inject commands via unspecified CAPF programs, aka Bug ID CSCum95493.

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

Local command injection vulnerability in the Certificate Authority Proxy Function (CAPF) CLI implementation of Cisco Unified Communications Manager versions 10.0(1) and earlier. Local users can inject arbitrary commands through unspecified CAPF programs due to insufficient input validation.

MitigationUpgrade to a Cisco Unified CM version beyond 10.0(1) that contains the fix. Limit local access to trusted personnel only and follow least-privilege principles for CLI access.

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
Local
Complexity
Low
Authentication
Single
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/AC:L/Au:S/C:C/I:C/A:C

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 installation directories, services, or use system inventory tools. Common locations include /usr/local/cm or check for 'Cisco Unified Communications Manager' processes or services.
    Affected if Cisco Unified Communications Manager software is found on the system
  2. Determine the installed CUCM version
    Run 'show version' at the CLI prompt if access is available, or check the installed packages/registry for the version string matching the pattern like '10.0(1)', '4.2', '3.3(5)', etc.
    Affected if The installed version matches any of: <= 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, or 4.2.2
  3. Verify if CAPF (Certificate Authority Proxy Function) is configured or enabled
    Check CUCM administration interface for CAPF service status, or query the CAPF CLI commands if available. CAPF is typically configured under Cisco Unified Serviceability > Tools > Feature Services.
    Affected if CAPF service is enabled or configured in the CUCM environment
  4. Check for local user access to the system
    Review local user accounts with CLI or operating system access to the CUCM server. Examine /etc/passwd or equivalent for local users, and check sudo/privilege configurations.
    Affected if Local user accounts exist with CLI access to the CUCM server (the vulnerability requires local access for exploitation)

A user is affected if Cisco Unified Communications Manager is installed with a version matching the affected list AND CAPF is enabled, while having local user accounts 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
Upgrade available Upgrade to a release after 10.0
Interim mitigation

Upgrade to a Cisco Unified CM version beyond 10.0(1) that contains the fix. Limit local access to trusted personnel only and follow least-privilege principles for CLI access.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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