Unified Communications ManagerApplication · Cisco
CVE-2014-3292
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 · uneditedThe Real Time Monitoring Tool (RTMT) implementation in Cisco Unified Communications Manager (Unified CM) allows remote authenticated users to (1) read or (2) delete arbitrary files via a crafted URL, aka Bug IDs CSCuo17302 and CSCuo17199.
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 confidenceThe Real Time Monitoring Tool (RTMT) in Cisco Unified CM contains a path traversal vulnerability allowing authenticated remote users to read or delete arbitrary files on the system via crafted URLs. This is a vertical privilege escalation where standard users can access system-level files outside their authorized scope.
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
all versionsCVSS 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
- Single
- Confidentiality
- Partial
- Integrity
- None
- Availability
- Partial
AV:N/AC:L/Au:S/C:P/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm RTMT is enabled on Unified CMLog into the Cisco Unified CM Administration interface and navigate to System > RTMT. Verify the Real Time Monitoring Tool service is enabled and running.Affected if RTMT service is enabled and accessible
-
Check if RTMT is exposed to networkIdentify the IP addresses or network segments that can reach the RTMT service. Default RTMT ports are 8080 and 8443. Use netstat or firewall rules to determine if these ports are listening on external interfaces.Affected if RTMT ports are bound to accessible network interfaces
-
Verify external access to RTMT portsFrom an external host, attempt to reach the RTMT web interface (https://<ucm-host>:8443/rtmt). Confirm whether the service is reachable from untrusted networks.Affected if RTMT is reachable from untrusted networks
-
Confirm user authentication contextDetermine if standard (non-admin) users have RTMT access. Check RTMT user group assignments under User Management > RTMT User Group in Cisco Unified CM Administration.Affected if Standard users can authenticate to RTMT
-
Assess network access controlsReview any existing firewall rules, ACLs, or URL filtering that may limit access to RTMT. Determine if traversal sequences (%2e%2e, ..) would be blocked by existing filters.Affected if No network restrictions or URL filtering blocks traversal patterns
If RTMT is enabled, accessible from the network, and standard users can authenticate to it, the environment is vulnerable to path traversal exploitation.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the relevant Cisco patch for Unified CM (refer to CSCuo17302/CSCuo17199). If patches are unavailable, restrict network access to RTMT ports and implement URL filtering to block traversal sequences.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2014-3292 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-3292 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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