Unified Communications ManagerApplication · Cisco
CVE-2014-8008
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 · uneditedAbsolute path traversal vulnerability in the Real-Time Monitoring Tool (RTMT) API in Cisco Unified Communications Manager (CUCM) allows remote authenticated users to read arbitrary files via a full pathname in an API command, aka Bug ID CSCur49414.
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 confidenceAbsolute path traversal vulnerability in Cisco CUCM's Real-Time Monitoring Tool (RTMT) API allows authenticated remote users to read arbitrary files on the system by providing full pathnames in API commands. The vulnerability stems from insufficient validation of file path inputs in the RTMT API, enabling attackers with valid credentials to access sensitive system files beyond the intended 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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco CUCM installationCheck for Cisco Unified Communications Manager directories or services on the system. Look for installation paths such as /opt/cisco or check for CUCM-related processes or services.Affected if CUCM is installed and the RTMT API is network-accessible
-
Verify RTMT service statusDetermine if the Real-Time Monitoring Tool service is running. On CUCM systems, this is typically handled by the RTMT service/process. Check via system service status or CUCM administration interface.Affected if RTMT service is running and accepting external connections
-
Check RTMT API network exposureIdentify open ports associated with RTMT. Default RTMT communication uses specific ports (typically 8443 for HTTPS, 8080 for HTTP in some configurations). Review firewall rules and listening services to determine if these ports are exposed externally.Affected if RTMT API ports are accessible from untrusted networks
-
Confirm external authentication accessVerify that RTMT API allows external authentication. Check whether the API accepts user credentials from remote sources and whether default or configured service accounts can authenticate remotely.Affected if RTMT accepts remote authentication credentials without additional network restrictions
A system is affected if Cisco CUCM is installed with RTMT enabled and the RTMT API interface is network-accessible to untrusted users, since all CUCM versions contain the path traversal flaw.
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 Cisco patch for CSCur49414 to the CUCM installation. If patching is immediately unavailable, restrict network access to the RTMT API interface using ACLs and consider disabling RTMT external access until the patch can be deployed.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8008 — 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-8008 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