Unified Communications ManagerApplication · Cisco
CVE-2014-2184
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 IP Manager Assistant (IPMA) component in Cisco Unified Communications Manager (Unified CM) allows remote attackers to obtain sensitive information via a crafted URL, aka Bug ID CSCun74352.
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 IP Manager Assistant (IPMA) component in Cisco Unified Communications Manager fails to properly sanitize user-supplied input in URLs, allowing remote unauthenticated attackers to access sensitive information through crafted requests.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm IPMA component is enabledAccess Cisco Unified CM Administration interface, navigate to Feature > IP Manager Assistant > IP Manager Assistant Settings, and verify if 'Enable IPMA' is checked/activatedAffected if IPMA is enabled and the server is network-accessible via HTTP/HTTPS
-
Check if IPMA port is listeningRun 'netstat -an | grep <IPMA_port>' or 'telnet <server> <port>' where IPMA typically uses port 8443 or 8080 for web servicesAffected if The IPMA service port is listening and accepting connections from untrusted networks
-
Verify web interface accessibilityAttempt to access 'https://< cucm_host >:8443/ipma/' or similar IPMA URLs from an untrusted network locationAffected if The IPMA web interface responds without authentication or shows sensitive configuration data
-
Review Cisco Unified CM versionIn Cisco Unified CM Administration, navigate to About > Security, or run 'show version' via CLI to identify the installed CUCM versionAffected if The installed version is any release prior to the Cisco fix for bug CSCun74352 (the CVE affects all versions per the advisory)
A user is affected if the IP Manager Assistant component is enabled and its web interface is accessible via HTTP/HTTPS from untrusted networks, regardless of which Cisco Unified CM version is running.
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 security update for Unified CM addressing Bug ID CSCun74352, or upgrade to a fixed version of Cisco Unified Communications Manager.
Fix this in Unified Communications Manager
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.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,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-2184 — 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-2184 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