dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2014-0741

MEDIUM · 6.2 CVSS v2.0 Published 2014-02-27
Fix available
A fix is available. Upgrade to after 10.0 or later.
See remediation →
64/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-import feature in the Certificate Authority Proxy Function (CAPF) CLI implementation in Cisco Unified Communications Manager (Unified CM) 10.0(1) and earlier allows local users to read or modify arbitrary files via a crafted command, aka Bug ID CSCum95461.

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

A local file inclusion vulnerability exists in the CAPF CLI certificate-import feature of Cisco Unified Communications Manager 10.0(1) and earlier. Local authenticated users can read or modify arbitrary files on the system by issuing a crafted command to the certificate-import functionality, effectively bypassing intended file access restrictions.

MitigationApply the appropriate Cisco patch for Unified CM (contact Cisco for specific version availability). If patching is immediately impractical, restrict CLI access to CAPF to only trusted administrators and monitor for suspicious certificate-import commands.

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
None

AV:L/AC:L/Au:S/C:C/I:C/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 Cisco Unified Communications Manager version
    Access the Cisco Unified CM administration interface or run 'show version' via CLI to retrieve the installed CUCM version number
    Affected if The installed version matches <= 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
  2. Verify CAPF service is enabled
    In Cisco Unified CM Administration, navigate to System > Service Parameters and check the status of the Certificate Authority Proxy Function (CAPF) service, or query via CLI using 'show service'
    Affected if CAPF service is running and accessible to authenticated users
  3. Confirm CLI access to CAPF is available
    Check if the 'certificate-import' command is accessible via the CLI interface for authenticated administrator accounts
    Affected if Authenticated local users have CLI access to the certificate-import functionality in CAPF
  4. Review logs for suspicious certificate-import commands
    Examine CAPF and system logs for certificate-import commands that reference unusual file paths outside the expected certificate directory
    Affected if Logs show certificate-import commands with directory traversal patterns or access to unexpected file locations

If the installed Cisco Unified Communications Manager version is one of the affected versions listed AND CAPF CLI certificate-import feature is accessible to authenticated users, the environment is vulnerable to local file inclusion.

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 appropriate Cisco patch for Unified CM (contact Cisco for specific version availability). If patching is immediately impractical, restrict CLI access to CAPF to only trusted administrators and monitor for suspicious certificate-import commands.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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