Unified Communications Domain Manager PlatformApplication · Cisco

CVE-2014-3380

MEDIUM · 5.0 CVSS v2.0 Published 2014-09-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges 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
Cisco Unified Communications Domain Manager Platform Software 4.4(.3) and earlier allows remote attackers to cause a denial of service (CPU consumption) by sending crafted TCP packets quickly, aka Bug ID CSCuo42063.

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

Cisco Unified Communications Domain Manager Platform Software versions 4.4(.3) and earlier contains a denial of service vulnerability where remote attackers can cause excessive CPU consumption by sending specially crafted TCP packets rapidly to the affected system, rendering services unavailable.

MitigationApply the Cisco security patch for bug ID CSCuo42063 to address this vulnerability. If patches are unavailable, implement network-level rate limiting or firewall controls to restrict unauthenticated TCP traffic to the affected platform.

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 Domain Manager PlatformApplication
Affected:= 4.4\(.3\)

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

AV:N/AC:L/Au:N/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Cisco Unified Communications Domain Manager Platform version
    Access the system administrative interface or use the command line interface (CLI) to query the software version. Typically via 'show version' or through the web-based administration portal under System > Version information.
    Affected if The installed version is 4.4.3 or any earlier version (4.4, 4.3, etc.)
  2. Confirm the exact version string matches affected release
    Verify the precise version number displayed matches the pattern 4.4(.3) meaning version 4.4.3 or any 4.4.x version up to and including 4.4.3, or version 4.4 without a minor release number.
    Affected if Version is 4.4.3, 4.4.2, 4.4.1, 4.4.0, or 4.4 (any 4.4.x release)
  3. Determine if the management interface is network accessible
    Check if the Cisco Unified Communications Domain Manager Platform management TCP ports (typically 443, 8443, or other admin ports) are exposed to untrusted networks. Use network scanning or review firewall rules.
    Affected if The management interface is reachable from untrusted or external networks without filtering
  4. Check for symptoms of TCP-based CPU exhaustion
    Monitor system CPU usage via 'show processes cpu history' or similar CLI command. Look for sustained high CPU consumption coinciding with inbound TCP traffic patterns.
    Affected if CPU utilization is abnormally high from inbound TCP traffic and services are slow or unresponsive

You are affected if the installed Cisco Unified Communications Domain Manager Platform version is 4.4.3 or any earlier 4.4.x release and the system is network-accessible to untrusted hosts.

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 Cisco security patch for bug ID CSCuo42063 to address this vulnerability. If patches are unavailable, implement network-level rate limiting or firewall controls to restrict unauthenticated TCP traffic to the affected platform.

Fix this in Unified Communications Domain Manager Platform 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-3380 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-3380 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