dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2014-0732

MEDIUM · 5.0 CVSS v2.0 Published 2014-02-20
Fix available
A fix is available. Upgrade to after 10.0 or later.
See remediation →
59/100
Remediation priority · Elevated
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
The Real Time Monitoring Tool (RTMT) web application in Cisco Unified Communications Manager (Unified CM) 10.0(1) and earlier does not properly enforce authentication requirements, which allows remote attackers to read application files via a direct request to a URL, aka Bug ID CSCum46495.

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

The Real Time Monitoring Tool (RTMT) web application in Cisco Unified Communications Manager 10.0(1) and earlier fails to properly enforce authentication requirements, allowing unauthenticated remote attackers to directly request application files via specific URLs and read sensitive data without credentials.

MitigationApply the Cisco patch for bug ID CSCum46495, or upgrade to a Cisco Unified Communications Manager version beyond 10.0(1) that includes the fix; alternatively, restrict network access to RTMT ports using firewall rules or ACLs until patching is feasible.

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

AV:N/AC:L/Au:N/C:P/I:N/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 RTMT web service availability
    Determine if the Real Time Monitoring Tool web interface is exposed by checking if ports 8443 or 443 are open on the CUCM server, or attempt to access the RTMT URL path (typically /rtmt) without credentials
    Affected if RTMT web interface is accessible without authentication redirecting to a login page
  2. Verify CUCM version
    Run the command 'show version' on the CUCM server CLI or check the installed version through the Cisco Unified Communications Manager Administration interface under the 'About' page
    Affected if The installed version matches one of the affected versions: 10.0(1) or earlier, or 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
  3. Confirm RTMT is enabled
    Log into Cisco Unified Communications Manager Administration and navigate to System > Enterprise Parameters, or check via CLI with 'run sql select name,value from processconfig where name like '%RTMT%''
    Affected if RTMT service is enabled and running on the system
  4. Test unauthenticated URL access
    Using a browser or curl tool, attempt to directly access RTMT file URLs such as /rtmt/jsp/.* without providing credentials or a session token
    Affected if Sensitive application files or data can be retrieved without authentication credentials being required
  5. Check network exposure
    Review firewall rules or ACLs to determine if RTMT web ports (8443, 443) are exposed to untrusted networks or the internet
    Affected if RTMT is reachable from untrusted network segments or the public internet

The environment is affected if Cisco Unified Communications Manager version is at or below 10.0(1) (or matches any listed affected version) AND the RTMT web application is accessible over the network without requiring authentication.

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 patch for bug ID CSCum46495, or upgrade to a Cisco Unified Communications Manager version beyond 10.0(1) that includes the fix; alternatively, restrict network access to RTMT ports using firewall rules or ACLs until patching is feasible.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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