dbcve.org
Unified Communications ManagerApplication · Cisco

CVE-2014-3319

MEDIUM · 6.8 CVSS v2.0 Published 2014-07-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable 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
Directory traversal vulnerability in the Real-Time Monitoring Tool (RTMT) in Cisco Unified Communications Manager (CM) 10.0(1) allows remote authenticated users to read arbitrary files via a crafted URL, aka Bug ID CSCup57676.

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

Directory traversal vulnerability in Cisco Unified Communications Manager's Real-Time Monitoring Tool (RTMT) allows authenticated users to craft URLs with traversal sequences (such as ../) to read arbitrary files on the system outside the intended web root directory.

MitigationApply the vendor patch from Cisco for CUCM 10.0(1). Additionally, restrict RTMT access to only essential authenticated users and consider network segmentation to limit exposure.

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\)

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
Single
Confidentiality
Complete
Integrity
None
Availability
None

AV:N/AC:L/Au:S/C:C/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 if Cisco Unified Communications Manager is installed
    Check for CUCM installation by looking for the Cisco Unified Communications Manager directory structure, typically under /opt or C:\Program Files\Cisco, or check for the 'Cisco Unified Serviceability' or 'RTMT' services running on the system
    Affected if CUCM is installed and running on the system
  2. Verify the CUCM version is 10.0(1)
    Access the CUCM Administration interface and navigate to the 'About' page, or use the CLI command 'show version' via the command line interface if you have administrative access, and check if the installed version equals 10.0(1)
    Affected if The installed CUCM version is exactly 10.0(1)
  3. Determine if RTMT is enabled and accessible
    Check if the Real-Time Monitoring Tool web interface is accessible by attempting to access the RTMT URL (typically on port 8443 or 443) or by checking the RTMT service status via the CUCM Serviceability interface
    Affected if RTMT web interface is enabled and accessible over the network
  4. Verify RTMT authentication is in use
    Confirm that RTMT requires authentication by attempting to access the RTMT interface without credentials and observing whether a login prompt appears, or check the RTMT security settings in the CUCM Administration interface
    Affected if RTMT is accessible with authenticated user access
  5. Confirm the RTMT web application is exposed
    Check network exposure of the RTMT web port (commonly 8443) by reviewing firewall rules, listening network services, or attempting a connection to the RTMT URL from an external perspective
    Affected if The RTMT web application port is exposed to network-accessible interfaces

The environment is affected if Cisco Unified Communications Manager version 10.0(1) is installed with RTMT enabled and accessible, allowing authenticated users to exploit directory traversal via crafted URLs.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch from Cisco for CUCM 10.0(1). Additionally, restrict RTMT access to only essential authenticated users and consider network segmentation to limit exposure.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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