dbcve.org
Unified Communications Domain ManagerApplication · Cisco

CVE-2013-1230

MEDIUM · 5.0 CVSS v2.0 Published 2013-05-01
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 allows remote attackers to cause a denial of service (CPU consumption) via a flood of malformed UDP packets, aka Bug ID CSCug47057.

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

This is a denial of service vulnerability in Cisco Unified Communications Domain Manager where malformed UDP packets sent in a flood cause excessive CPU consumption on the affected system, rendering it unavailable.

MitigationApply the vendor patch from Cisco for bug ID CSCug47057, or implement network-level filtering/rate limiting for malformed UDP traffic at the perimeter firewall to mitigate the attack.

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 ManagerApplication
Affected:all versions

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 Cisco Unified Communications Domain Manager installation
    Check system inventory or running services for Cisco Unified Communications Domain Manager (sometimes abbreviated as CUCDM or Cisco UC Domain Manager). On Linux, search for process names containing 'ucd' or 'domainmanager' using 'ps aux | grep -i ucd' or 'ps aux | grep -i domain'. Check installed packages if using a package manager.
    Affected if The product is present on the system - all versions are affected by this CVE
  2. Observe system CPU usage
    Monitor CPU utilization on the affected system using commands like 'top', 'htop', or 'uptime'. Look for sustained high CPU usage that is unexplained by normal operations. Check CPU load averages over time with 'uptime' or 'sar'.
    Affected if CPU consumption is abnormally high and correlates with UDP traffic processing
  3. Capture and inspect UDP traffic
    Use packet capture tools such as tcpdump or Wireshark to capture UDP packets flowing toward the affected system. Example: 'tcpdump -i <interface> -w capture.pcap udp'. Inspect the capture for malformed or malformed-looking UDP packets (invalid headers, unusual payloads, or packets that violate UDP protocol specs).
    Affected if Malformed UDP packets are being received by the system
  4. Check for UDP flood patterns
    Use 'netstat -anu' or 'ss -uan' to observe UDP socket statistics. Monitor UDP packet rates using tools like 'iftop', 'nethogs', or by analyzing flow data from network devices. Look for high volumes of incoming UDP traffic targeting the Cisco Unified Communications Domain Manager service ports.
    Affected if A flood of incoming UDP packets is detected toward the affected host
  5. Review system and application logs
    Check system logs (/var/log/messages, /var/log/syslog) and any application-specific logs for Cisco Unified Communications Domain Manager. Look for error messages, warnings about malformed packets, or indicators of service degradation. Search for keywords like 'UDP', 'malformed', 'error', 'cpu', 'high', 'denial'.
    Affected if Logs indicate processing issues related to UDP traffic or service availability problems

If Cisco Unified Communications Domain Manager is installed and you observe high CPU consumption correlated with incoming malformed UDP traffic, your environment is affected by CVE-2013-1230.

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 bug ID CSCug47057, or implement network-level filtering/rate limiting for malformed UDP traffic at the perimeter firewall to mitigate the attack.

Fix this in Unified Communications Domain Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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