Unified Communications ManagerApplication · Cisco

CVE-2013-3453

HIGH · 7.8 CVSS v2.0 Published 2013-08-22
Fix available
A fix is available. Upgrade to after 8.6 or later.
See remediation →
87/100
Remediation priority · High
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
Memory leak in Cisco Unified Communications Manager IM and Presence Service before 8.6(5)SU1 and 9.x before 9.1(2), and Cisco Unified Presence, allows remote attackers to cause a denial of service (memory and CPU consumption) by making many TCP connections to port (1) 5060 or (2) 5061, aka Bug ID CSCud84959.

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 confidence

Memory leak in Cisco Unified Communications Manager IM and Presence Service and Cisco Unified Presence allows remote attackers to cause denial of service by establishing many TCP connections to SIP ports 5060 or 5061, leading to memory and CPU exhaustion.

MitigationUpgrade to Cisco Unified Communications Manager IM and Presence Service 8.6(5)SU1/9.1(2) or later. Implement rate limiting on SIP ports and firewall rules to restrict excessive connection attempts.

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
Affected:<= 8.6\(4\)= 3.3\(5\)= 3.3\(5\)sr1= 3.3\(5\)sr2a= 4.1\(3\)= 4.1\(3\)sr1= 4.1\(3\)sr2= 4.1\(3\)sr3= 4.1\(3\)sr4= 4.2= 4.2.1= 4.2.2
Unified PresenceApplication
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
Complete

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

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

  1. Identify installed Cisco product
    Determine if the system runs Cisco Unified Communications Manager (CUCM) or Cisco Unified Presence (CUP) by checking installed software packages or running 'show version' on the Cisco device
    Affected if The product is Cisco Unified Presence (any version) or Cisco Unified Communications Manager version 8.6(4) and below, 3.3(5)/3.3(5)sr1/3.3(5)sr2a, 4.1(3) through 4.1(3)sr4, or 4.2/4.2.1/4.2.2
  2. Verify SIP service is enabled
    Check if the SIP service is active by querying the service status or reviewing the configuration for SIP port bindings on ports 5060 (UDP/TCP) and 5061 (TLS)
    Affected if SIP service is enabled and listening on ports 5060 or 5061
  3. Check network exposure of SIP ports
    Scan or review firewall rules to determine if SIP ports 5060 and 5061 are exposed to untrusted networks or the internet
    Affected if SIP ports 5060 or 5061 are accessible from external or untrusted networks
  4. Monitor for connection exhaustion
    Observe system resources and TCP connection counts on the SIP service using 'show connections' or equivalent monitoring tools
    Affected if A high number of concurrent TCP connections to SIP ports is observed, leading to memory or CPU exhaustion

You are affected if you run Cisco Unified Presence (any version) or a vulnerable Cisco Unified Communications Manager version with SIP ports 5060/5061 exposed to the network, as the memory leak can be triggered by establishing many TCP connections to these ports.

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
Upgrade available Upgrade to a release after 8.6
Interim mitigation

Upgrade to Cisco Unified Communications Manager IM and Presence Service 8.6(5)SU1/9.1(2) or later. Implement rate limiting on SIP ports and firewall rules to restrict excessive connection attempts.

Fix this in Unified Communications Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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