Unity ConnectionApplication · Cisco
CVE-2014-0664
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 server in Cisco Unity Connection allows remote authenticated users to cause a denial of service (CPU consumption) via unspecified IMAP commands, aka Bug ID CSCul49976.
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 vulnerability exists in the IMAP service component of Cisco Unity Connection. An authenticated remote user can send specific (unspecified) IMAP commands to the server, causing excessive CPU consumption and resulting in denial of service. The attack requires valid authentication credentials.
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
Unity ConnectionApplication
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
- None
- Integrity
- None
- Availability
- Complete
AV:N/AC:L/Au:S/C:N/I:N/A:C
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 Cisco Unity Connection is installedCheck system for Cisco Unity Connection installation - look for the product in installed software or check for Unity Connection services running on the serverAffected if Unity Connection is present on the system
-
Verify IMAP service is enabledCheck if the IMAP service component is enabled on the Unity Connection server - this can be done via the Unity Connection administration interface under IMAP settings, or by checking if IMAP ports (typically 143 or 993) are listeningAffected if IMAP service is enabled and listening on the network
-
Check current version against patchesDetermine the installed version of Cisco Unity Connection via the administration console or CLI (using 'show version' command), then verify if the system has the vendor patches applied for CVE-2014-0664Affected if The installed version has not received the security patch for this CVE
-
Review IMAP authentication settingsInspect IMAP authentication configuration to confirm valid user accounts can authenticate to the IMAP service - check authentication method settings and user account status in Unity ConnectionAffected if IMAP authentication is active and allows standard user access without additional restrictions
A user is affected if Cisco Unity Connection with an unpatched version has IMAP service enabled and accessible with valid authentication credentials.
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 dataIf a vendor patch is unavailable, consider disabling or restricting IMAP access, implementing rate limiting on IMAP connections, or isolating the service via network segmentation. Ensure strong authentication controls are in place for IMAP access.
Fix this in Unity Connection
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0664 — 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-0664 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