dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2014-0740

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 →
77/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
Cross-site request forgery (CSRF) vulnerability in the Call Detail Records Analysis and Reporting (CAR) interface in the OS Administration component in Cisco Unified Communications Manager (Unified CM) 10.0(1) and earlier allows remote attackers to hijack the authentication of administrators for requests that make administrative changes, aka Bug ID CSCun00701.

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

CSRF vulnerability in Cisco Unified Communications Manager's CAR (Call Detail Records Analysis and Reporting) interface allows remote attackers to execute administrative actions by tricking authenticated administrators into visiting malicious pages, leveraging the trusted session to send forged requests.

MitigationApply Cisco's patch for CSCun00701 or upgrade to a Cisco Unified CM version later than 10.0(1). Additionally, implement anti-CSRF tokens in the CAR interface and consider deploying CSRF protection at the web application firewall layer as a compensating control.

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

AV:N/AC:M/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 Cisco Unified CM version
    Access the Cisco Unified CM Administration interface and navigate to the About page, or use the CLI command 'show version' to retrieve the installed software version.
    Affected if The installed version is 10.0(1) or earlier, or matches one of these specific versions: 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 CAR interface is enabled
    In the Cisco Unified CM Administration interface, navigate to the CAR (Call Detail Records Analysis and Reporting) service status page or check the application list to confirm CAR is listed as active.
    Affected if The CAR interface is enabled and running on the system.
  3. Confirm CAR web interface accessibility
    Attempt to access the CAR web portal URL (typically at /car/ on the CUCM host) using a browser or curl command to verify the interface responds to HTTP/HTTPS requests.
    Affected if The CAR web interface is reachable over the network.
  4. Verify administrator authentication is configured
    Check the Cisco Unified CM user management section to confirm administrator accounts exist and have access to the CAR interface, as the CSRF attack requires an authenticated session.
    Affected if Administrative users with CAR access are configured and can log in to the CAR interface.

All conditions must be true for exploitation: the installed Cisco Unified CM version must be in the affected list, the CAR interface must be enabled, and it must be accessible to potential attackers who could trick an authenticated administrator into visiting a malicious page.

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 Cisco's patch for CSCun00701 or upgrade to a Cisco Unified CM version later than 10.0(1). Additionally, implement anti-CSRF tokens in the CAR interface and consider deploying CSRF protection at the web application firewall layer as a compensating control.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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