dbcve.org
Telepresence Tc SoftwareApplication · Cisco

CVE-2013-3377

HIGH · 7.8 CVSS v2.0 Published 2013-06-21
Fix available
A fix is available. Upgrade to after 5.1.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
Cisco TelePresence TC Software before 5.1.7 and TE Software before 4.1.3 allow remote attackers to cause a denial of service (device reload) via crafted SIP packets, aka Bug ID CSCue01743.

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

Cisco TelePresence TC Software before 5.1.7 and TE Software before 4.1.3 contain a vulnerability in SIP packet processing that allows remote, unauthenticated attackers to send specially crafted SIP packets causing the device to reload, resulting in denial of service.

MitigationUpgrade to Cisco TelePresence TC Software 5.1.7 or later, or TE Software 4.1.3 or later. If immediate patching is not feasible, consider SIP packet filtering at network perimeter devices to block malicious SIP traffic.

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
Telepresence Tc SoftwareApplication
Affected:<= 5.1.6= 5.0.0= 5.0.1= 5.0.2= 5.1.0= 5.1.1= 5.1.2= 5.1.3= 5.1.4= 5.1.5
Ip Video Phone E20Hardware / appliance
Affected:all versions
Telepresence Codec C40Hardware / appliance
Affected:all versions
Telepresence Codec C60Hardware / appliance
Affected:all versions
Telepresence Codec C90Hardware / appliance
Affected:all versions
Telepresence Ex60Hardware / appliance
Affected:all versions
Telepresence Ex90Hardware / appliance
Affected:all versions
Telepresence Mx200Hardware / appliance
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 the Cisco TelePresence device model
    Access the device CLI or web interface to determine the exact hardware model (e.g., E20, C40, C60, C90, Ex60, Ex90, Mx200, or TC/TE software device)
    Affected if The device is any of these models: E20, C40, C60, C90, Ex60, Ex90, or Mx200 (all versions affected)
  2. Determine the software version for TC or TE devices
    Run 'show version' command in the device CLI or check the web interface admin page to retrieve the installed software version
    Affected if For TC Software: version is 5.0.0, 5.0.1, 5.0.2, 5.1.0, 5.1.1, 5.1.2, 5.1.3, 5.1.4, 5.1.5, or 5.1.6. For TE Software: version is 4.1.0, 4.1.1, or 4.1.2
  3. Check if SIP signaling is enabled
    Review the device configuration via CLI command 'show sip' or check the SIP settings in the web interface under the call settings or network configuration section
    Affected if SIP protocol is enabled and configured on the device (the vulnerability is triggered by specially crafted SIP packets)
  4. Verify the device is reachable on SIP ports
    Check if the device has SIP port 5060 (UDP/TCP) open and listening by running 'show network connections' or scanning the device IP for open ports
    Affected if The device accepts SIP traffic on any interface, as unauthenticated remote attackers can send malicious packets to trigger the reload

The environment is affected if the device is an E20, C40, C60, C90, Ex60, Ex90, or Mx200 (any version), or if running TC Software version 5.0.0-5.1.6 or TE Software version 4.1.0-4.1.2, and SIP is enabled and reachable on the network.

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 5.1.6
Interim mitigation

Upgrade to Cisco TelePresence TC Software 5.1.7 or later, or TE Software 4.1.3 or later. If immediate patching is not feasible, consider SIP packet filtering at network perimeter devices to block malicious SIP traffic.

Fix this in Telepresence Tc Software Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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